All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christoph A." <casmls@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List <netfilter-devel@vger.kernel.org>
Subject: Re: security impact of creating rulesets with iptables (cmd)
Date: Mon, 10 Aug 2009 01:28:09 +0200	[thread overview]
Message-ID: <4A7F5B89.9030105@gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.00.0908100000110.23833@fbirervta.pbzchgretzou.qr>

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

On 10.08.2009 00:18, Jan Engelhardt wrote:
> Even if you manage to avoid temporary Windows Of Opportunity For 
> Attackers does not mean all novice users are able to do the same. Hence 
> it is easier to just use iptables-restore and need not worry about 
> atomicity within a given table.

thanks for your fast reply!
Christoph A.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-08-09 23:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09 21:43 security impact of creating rulesets with iptables (cmd) Christoph A.
2009-08-09 22:18 ` Jan Engelhardt
2009-08-09 23:28   ` Christoph A. [this message]
2009-08-10  6:58 ` Patrick McHardy
2009-08-10  8:31   ` Jan Engelhardt

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=4A7F5B89.9030105@gmail.com \
    --to=casmls@gmail.com \
    --cc=jengelh@medozas.de \
    --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.