All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: SBlaze <dagent.geo@yahoo.com>
Cc: Ralf Spenneberg <lists@spenneberg.org>,
	nf <netfilter@lists.netfilter.org>,
	cc@belfordhk.com
Subject: Re: Need help have some questions...
Date: Mon, 18 Aug 2003 16:52:23 -0400	[thread overview]
Message-ID: <20030818205223.GA3993@cannon.eng.us.uu.net> (raw)
In-Reply-To: <20030818201333.57194.qmail@web40202.mail.yahoo.com>

On Mon, Aug 18, 2003 at 01:13:33PM -0700, SBlaze wrote:

> To Ralf, the netfilter team, and the whole of the OS community
> 
> How am I supposed to proxy apache? Why should I have to? Is it not a firewalls
> job to protect a system(and LAN behind it)? This is a very valid form of
> protection I'm asking for here.

First of all, cool down. Secondly, read up on layered model of networking
and try to understand, each layer and its functionality, like, IP is meant
for routing, TCP is meant for reliable end to end communication and HTTP
is meant for retrieval of the hyper text (and images and audio and video...).

Once you get there, you'll understand the goals of netfilter and the layer(s)
it's supposed to function upon. However, there have been some adhoc 
developements here and there by means of different (pom) modules which have
extended the borders of what netfilter can/should do like the "string" module.
But when you get to the bits and bytes of how things work you would realize
that, eg, the "string" module kills your system by its extensive scan of
the packets. It does not know that an "invalid" HTTP request happens at the
very beginning of the HTTP communication after a "GET" command... And again
because of some technical issues like fragmentation (which can be found in the
readings you've already done) this "string" module is not bullet-proof for
catching the HTTP requests you don't like.

What Ralf mentioned earlier is absolutely valid. If you want to filter based
on an application specific property (eg, "Get cmd.exe", or whatever the M$
hacks look like) then you need to make use of a filter at the application
level. In this case, a process which terminates the HTTP dialog, looks for
(in)valid requests and acts upon it accordingly.

This is a .02$ explanation you asked for.

Ramin


  reply	other threads:[~2003-08-18 20:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1061192932.1915.10.camel@kermit>
2003-08-18 20:13 ` Need help have some questions SBlaze
2003-08-18 20:52   ` Ramin Dousti [this message]
2003-08-23 20:51     ` SBlaze
2003-08-25  3:24       ` Ramin Dousti
2003-08-25 20:05         ` SBlaze
2003-08-25 20:30           ` Ralf Spenneberg
2003-08-25 20:39             ` SBlaze
2003-08-25 20:57               ` Ralf Spenneberg
2003-08-25 22:40                 ` Ramin Dousti
2003-08-25 22:53                   ` SBlaze
2003-08-25 23:02                     ` Ramin Dousti
2003-08-25 22:35             ` Ramin Dousti
2003-08-25  5:54       ` Ralf Spenneberg
2003-08-18 20:53   ` Wallwork, Nathan
2003-08-18 21:09   ` Ralf Spenneberg
2003-08-18 21:14   ` Frank Smith
2003-08-15  9:29 SBlaze
2003-08-15 10:02 ` Ralf Spenneberg
2003-08-15 22:09   ` SBlaze

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=20030818205223.GA3993@cannon.eng.us.uu.net \
    --to=ramin@cannon.eng.us.uu.net \
    --cc=cc@belfordhk.com \
    --cc=dagent.geo@yahoo.com \
    --cc=lists@spenneberg.org \
    --cc=netfilter@lists.netfilter.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.