From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: SECURITY ADVISORY: outgoing firewall accepts packets unintendedly
Date: Sun, 12 Aug 2012 20:47:16 +0200 [thread overview]
Message-ID: <1344797236.19132.15.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <502389E2.9030409@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
Removed that unused variable.
http://git.ipfire.org/?p=people/ms/ipfire-2.x.git;a=commitdiff;h=4e2bce180421f90ab45ed71d00d2bbf902c407ee
On Thu, 2012-08-09 at 11:58 +0200, Bernhard Bitsch wrote:
> Why are there settings for chain policy? They are not used and cannot be set by
> a iptables command, but would be useful.
next parent reply other threads:[~2012-08-12 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <502389E2.9030409@gmx.de>
2012-08-12 18:47 ` Michael Tremer [this message]
2012-08-07 14:53 Michael Tremer
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=1344797236.19132.15.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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