netdev - Re: follow-up: discrepancy with POSIX

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] [day] [month] [year] [list]

Message-ID: <12044.1190234012@turing-police.cc.vt.edu>
Date:	Wed, 19 Sep 2007 16:33:32 -0400
From:	Valdis.Kletnieks@...edu
To:	Rick Jones <rick.jones2@...com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Ulrich Drepper <drepper@...hat.com>,
	netdev <netdev@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: follow-up: discrepancy with POSIX

On Wed, 19 Sep 2007 11:38:57 PDT, Rick Jones said:

> One has to set their way-back machine pretty far back to find the *BSD 
> bits which used 0.0.0.0 as the "all nets, all subnets" (to mis-use a 
> term) broadcast IPv4 address when sending.  Perhaps as far back as the 
> time before HP-UX 7 or SunOS4.  The bit errors in my dimm memory get 
> pretty dense that far back...

That would be BSD4.2 - BSD4.3 went to all-ones, and it *was* quite the
little mess if you had both flavors of boxes on the same subnet at the same
time, it would packet-storm *quite* easily.

Content of type "application/pgp-signature" skipped