netdev - Re: Error: an inet prefix is expected rather than "0/0".

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m34p3door9.fsf@maximus.localdomain>
Date:	Wed, 15 Oct 2008 17:35:06 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Stephen Hemminger <shemminger@...tta.com>,
	Krzysztof Oledzki <ole@....pl>, netdev@...r.kernel.org
Subject: Re: Error: an inet prefix is expected rather than "0/0".

Herbert Xu <herbert@...dor.apana.org.au> writes:

> How about just keeping Alexey's code? POSIX doesn't restrict
> the IP address format command utilities should accept.  So to
> me 127.2.0.0 is a perfectly acceptable interpretation of the
> partial address 127.2.

Then it would be better to disallow such things. The normal meaning
for "127.2" was always 127.0.0.2, and it was widely documented and
used (though perhaps in RFCs, not in POSIX). Some people use "10.1"
syntax all the time.

> This also has the benefit of not breaking any existing scripts
> that already work.  The scripts which are broken will remain
> broken which doesn't surprise anyone.

Any script which uses 127.2 to mean 127.2.0.0 is IMHO broken, though
I have never seen anything like that.

Rules always have been simple:
10	- 10.0.0.0
10.1	- 10.0.0.1
10.1.2	- 10.0.1.2

If it can't stay this way, lets remove this shortened notation
completely.
-- 
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html