netdev - Re: "[RFC PATCH net-next 2/2] Reduce localhost to 127.0.0.0/16"

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 for Android: free password hash cracker in your pocket

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

Message-ID: <9d2898f5-e5dc-a2ff-168d-22c69cca5f01@gmail.com>
Date:   Fri, 13 Sep 2019 11:01:59 -0600
From:   David Ahern <dsahern@...il.com>
To:     Dave Taht <dave.taht@...il.com>,
        Mark Smith <markzzzsmith@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: "[RFC PATCH net-next 2/2] Reduce localhost to 127.0.0.0/16"

On 9/13/19 10:14 AM, Dave Taht wrote:
> it came out that cumulus and a few others were possibly using high
> values of 127.x for switch chassis addressing, but we haven't got any
> documentation on how that works yet.

Not Cumulus.

I noted I am aware of 2 products from my history that use 127.x
addresses for communications within a box - e.g., to a bmc - that your
patch could break. Really it was meant as a data point that there are
released products that would be affected.