From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Phil Oester <kernel@linuxace.com>
Cc: Jorge Davila <davila@nicaraguaopensource.com>,
netfilter-devel@lists.netfilter.org,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH] Unspecified proto should print as "all" in iptables -L
Date: Thu, 03 May 2007 19:45:19 +0200 [thread overview]
Message-ID: <463A1FAF.5060207@gmx.net> (raw)
In-Reply-To: <20070503173121.GA7998@linuxace.com>
On 03.05.2007 19:31, Phil Oester wrote:
> On Thu, May 03, 2007 at 06:33:47PM +0200, Carl-Daniel Hailfinger wrote:
>> On 03.05.2007 18:16, Jorge Davila wrote:
>>> Well, it's because some users inside the internal networks under my
>>> administration visit http://www.grc.com/ and run the Shields Up! to see
>>> the open ports in the gateways and they see the port 0 open. That was
>>> the reason to apply the rule.
>> Ah cool, that's another datapoint when trying to guess the firewall
>> ruleset. Port 0 not filtered roughly means "default policy is ACCEPT".
>> (Well, not quite. But close.)
>
> Let's be clear here...we aren't talking about _PORT_ zero. We're talking
> about _PROTOCOL_ zero. Can you please elaborate on the specific need
> to filter _PROTOCOL_ zero?
Sorry, my bad. There is no specific need on my side. It's just that
some creative use of nmap enables me to learn more about target systems.
I am entirely happy with the current situation.
Regards,
Carl-Daniel
next prev parent reply other threads:[~2007-05-03 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 22:02 [PATCH] Unspecified proto should print as "all" in iptables -L Phil Oester
2007-04-29 23:06 ` Pablo Neira Ayuso
2007-04-30 8:38 ` Jan Engelhardt
2007-04-30 17:13 ` Phil Oester
2007-04-30 17:25 ` Jan Engelhardt
2007-04-30 17:36 ` Phil Oester
2007-04-30 18:17 ` Jorge Davila
2007-04-30 20:09 ` Phil Oester
2007-05-03 16:16 ` Jorge Davila
2007-05-03 16:33 ` Carl-Daniel Hailfinger
2007-05-03 17:31 ` Phil Oester
2007-05-03 17:45 ` Carl-Daniel Hailfinger [this message]
2007-06-02 18:49 ` How to match protocol 0 Jan Engelhardt
2007-06-02 21:19 ` 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=463A1FAF.5060207@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=davila@nicaraguaopensource.com \
--cc=jengelh@linux01.gwdg.de \
--cc=kernel@linuxace.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pablo@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.