From: Thomas Jacob <jacob@internet24.de>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Plans for future iptables versions / jumpset feature
Date: Thu, 22 May 2008 22:47:16 +0200 [thread overview]
Message-ID: <20080522204716.GA29008@internet24.de> (raw)
In-Reply-To: <4835D511.7030503@trash.net>
On Thu, May 22, 2008 at 10:18:25PM +0200, Patrick McHardy wrote:
> Not implemented yet, but I'm probably going to add this as an option
> (since it may affect the choice of data structure). For jumps its
> tricky though because loop detection has to be performed.
I don't see why this always has to be performed. There so many ways
to break your system when you're root, so being required to define a loop
free rule sets after specifying some kind of "yes I really want to"-
option should be that much of a burden. As far as I understand
the code, the loop checking at the moment is done in userspace, so
nobody stops you from simply removing that part from the iptables
code.
next prev parent reply other threads:[~2008-05-22 20:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 19:00 Plans for future iptables versions / jumpset feature Thomas Jacob
2008-05-22 19:18 ` Patrick McHardy
2008-05-22 19:57 ` Jan Engelhardt
2008-05-22 20:15 ` Patrick McHardy
2008-05-22 20:27 ` Thomas Jacob
2008-05-22 20:14 ` Thomas Jacob
2008-05-22 20:18 ` Patrick McHardy
2008-05-22 20:47 ` Thomas Jacob [this message]
2008-05-22 20:51 ` Patrick McHardy
2008-05-22 21:43 ` Thomas Jacob
2008-05-23 11:55 ` Nishit Shah
2008-05-23 12:15 ` Patrick McHardy
2008-05-23 12:47 ` Thomas Jacob
2008-05-23 13:28 ` Patrick McHardy
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=20080522204716.GA29008@internet24.de \
--to=jacob@internet24.de \
--cc=kaber@trash.net \
--cc=netfilter-devel@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.