Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Daniel Chemko <dchemko@smgtec.com>
Cc: firewalldude@newkirk.us, netfilter@lists.netfilter.org,
	netfilter-devel@lists.netfilter.org
Subject: RE: A humble proposal
Date: Fri, 26 Sep 2003 09:21:58 +0200	[thread overview]
Message-ID: <1064560917.3997.26.camel@porky> (raw)
In-Reply-To: <7C9884991ADAE0479C14F10C858BCDF5122E53@alderaan.smgtec.com>

[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]

Le ven 26/09/2003 à 02:19, Daniel Chemko a écrit :
> I had a thought about this, and I see a lot of work taking this
> approach.
> 
> How about this:
> 
> Write a jump target that applies only inside the filter table, since the
> first revision would just implement filtering control.
> 
> The module itself would be initialized by a userspace tool be adding
> rules. An example would be:
> 
> iptables -I INPUT -m expire --expire-condition timer=6000 --expire-id
> 12123124325 --source 192.168.1.1/24 -j ACCEPT
> iptables -I OUTPUT -m expire --expire-condition timer=6000 --expire-id
> 12123124326 --destination 192.168.1.1/24 -j ACCEPT

Great, but Have you any idea of the induced overload ? (I've never work
with dynamic rules).

> - The CONNTRACK entries for the allowed sessions are not dropped. Once
> again, it would be nice if the jump module could clean up the CONNTRACK
> entry.
> My humble suggestion would be that this should be handled in the
> stateful
> connection tracking - If a session is authenticated and certain
> connections
> allowing different chains to be traversed based on the mark found.

From my point of view this is a good idea for a mono user machine land.
But I think this appproach is for more too restrictive and too unsecure.

First, lot's of people use "terminal server" (X remote server, rdesktop,
cytrix,...) so you've got different people coming from the same IP who
should have dissociated IPs. In such a case, the permissions of these
users is the sum of the permissions of all users. It's really unsecure.

Second, you encounter harsh limitation with Full multiuser server. It's
a nice security feature to be able to say for example :
  - Clamav daemon can connect directly to sites providing antivirus
pattern update
  - Other users can't go directly out by http.
It's a small example taken from my test environnement of NuFW, but I
think it shows what can be done.

BR,
-- 
Eric Leblond
Nufw, Now User Filtering Works (http://www.nufw.org)

[-- Attachment #2: Ceci est une partie de message numériquement signée. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-09-26  7:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26  0:19 A humble proposal Daniel Chemko
2003-09-26  7:21 ` Eric Leblond [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-26 11:53 A Humble Proposal John A. Sullivan III
2003-09-24 10:57 John A. Sullivan III
2003-09-23 16:13 A humble proposal Daniel Chemko
2003-09-23 16:39 ` Eric Leblond
2003-09-23 21:10 ` Joel Newkirk
2003-10-02 19:51 ` Harald Welte
2003-10-02 21:26   ` Eric Leblond

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=1064560917.3997.26.camel@porky \
    --to=eric@regit.org \
    --cc=dchemko@smgtec.com \
    --cc=firewalldude@newkirk.us \
    --cc=netfilter-devel@lists.netfilter.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox