From: Amin Azez <azez@ufomechanic.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Phil Oester <kernel@linuxace.com>, netfilter-devel@lists.netfilter.org
Subject: Re: iptables 1.3.6 not using /etc/networks
Date: Wed, 29 Nov 2006 14:09:06 +0000 [thread overview]
Message-ID: <456D9482.30205@ufomechanic.net> (raw)
In-Reply-To: <4560F02C.4040905@netfilter.org>
* Pablo Neira Ayuso wrote, On 20/11/06 00:00:
> Laurence J. Lane wrote:
>> On 11/12/06, Phil Oester <kernel@linuxace.com> wrote:
>>
>>> Not sure offhand how we can satisfy both cases here, but I'd posit
>>> that more people use x.x.x/24 than use foonet/x notation.
>> I have another bug report saying it breaks stuff from /etc/hosts too.
>>
>> How about something like this? I assume valid IP characters are in the
>> range of 0-9 and a dot. This will skip pad_cidr() if any characters
>> outside of that range are encountered. Plain bad IP addresses are
>> apparently validated elsewhere. Of course, I could be wrong about all
>> of this.
>
> Apparently /etc/host accepts entries composed of dots, e.g.
>
> foo.machine 192.168.100.100
>
> So this assumption can be OK as soon as nobody is using such notation.
I do, so do lots of web developers I know; it helps them test websites
under the correct domain.
Does the patch you suggested depend on this not being the case?
Sam
next prev parent reply other threads:[~2006-11-29 14:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 1:25 iptables 1.3.6 not using /etc/networks Laurence J. Lane
2006-11-12 2:35 ` Laurence J. Lane
2006-11-12 17:33 ` Phil Oester
2006-11-12 19:36 ` Alexey Toptygin
2006-11-12 19:43 ` Phil Oester
2006-11-13 0:58 ` Alexey Toptygin
2006-11-13 7:23 ` Martijn Lievaart
2006-11-13 15:50 ` Alexey Toptygin
2006-11-13 20:20 ` Martijn Lievaart
2006-11-13 21:23 ` Alexey Toptygin
2006-11-14 9:06 ` offtopic " Amin Azez
2006-11-14 9:24 ` Benny Amorsen
2006-11-13 17:12 ` Phil Oester
2006-11-13 17:56 ` Alexey Toptygin
2006-11-13 19:50 ` scott comer (sccomer)
2006-11-18 22:09 ` Laurence J. Lane
2006-11-18 22:12 ` Laurence J. Lane
2006-11-20 0:00 ` Pablo Neira Ayuso
2006-11-23 14:10 ` Patrick McHardy
2006-11-23 20:56 ` Pablo Neira Ayuso
2006-11-24 5:55 ` Phil Oester
2006-11-24 8:43 ` Patrick McHardy
2006-11-29 4:44 ` Phil Oester
2006-11-29 12:50 ` Patrick McHardy
2006-11-29 14:09 ` Amin Azez [this message]
2006-11-29 14:21 ` Pablo Neira Ayuso
2006-11-19 20:34 ` Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2006-11-13 17:00 Alexey Toptygin
[not found] <200611131926.kADJPxur030380@mail3.jubileegroup.co.uk>
2006-11-14 10:17 ` G.W. Haywood
2006-11-14 19:28 ` Grant Coady
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=456D9482.30205@ufomechanic.net \
--to=azez@ufomechanic.net \
--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.