From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Query: Can Netfilter inspect xml soap traffic
Date: Tue, 25 Mar 2008 12:35:49 -0500 [thread overview]
Message-ID: <47E937F5.9050300@riverviewtech.net> (raw)
In-Reply-To: <47E93762.4040107@riverviewtech.net>
On 03/25/08 12:33, Taylor, Grant wrote:
> I would like to see developers write their applications with
> documentation (be it auto generated or not) that indicates what type of
> traffic (and parameters there on) they expect to see and need to
> function correctly. I'd like to then take said documentation and use it
> to build rules for a simple ALG that will pass any valid requests in to
> the back end application while correctly handling erroneous traffic. I
> think said ALGs could easily function as a proxy with some simple rules
> as to what is and is not allowed to pass through the ALG.
Note: I don't think that the rules for the ALG should be auto generated
on demand from the original code or class as this will be a performance
hit for systems. These rules need to be defined in a batch operation.
Now that batch operation could load the back end class and call a method
that will return what it is expecting to dynamically build the rules
once a night or when ever things are updated.
Grant. . . .
next prev parent reply other threads:[~2008-03-25 17:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 15:01 Query: Can Netfilter inspect xml soap traffic william fitzgerald
2008-03-25 16:42 ` Grant Taylor
2008-03-25 17:04 ` william fitzgerald
2008-03-25 17:25 ` Grant Taylor
2008-03-25 17:33 ` Grant Taylor
2008-03-25 17:35 ` Grant Taylor [this message]
2008-03-25 19:56 ` Benny Amorsen
2008-03-25 20:13 ` Grant Taylor
2008-03-26 16:39 ` william fitzgerald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E937F5.9050300@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.