netdev - Re: [RFC PATCH] ipv6: Use dev_addr in stable-privacy address generation

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: <20200327.154609.741168661523502246.davem@davemloft.net>
Date:   Fri, 27 Mar 2020 15:46:09 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     brambonne@...gle.com
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org, kuba@...nel.org,
        hannes@...essinduktion.org, netdev@...r.kernel.org,
        lorenzo@...gle.com, jeffv@...gle.com
Subject: Re: [RFC PATCH] ipv6: Use dev_addr in stable-privacy address
 generation

From: Bram Bonné <brambonne@...gle.com>
Date: Fri, 27 Mar 2020 12:50:07 +0100

> Could you help me understand the use cases where the admin / user
> chooses to use MAC address randomization, but still wants an IPv6
> link-local address that remains stable across these networks? My
> assumption was that the latter would defeat the purpose of the former,
> though it's entirely possible that I'm missing something.

Someone could renumber all of their MACs using a certain numbering
scheme, but that would not ensure the kind of uniqueness that the
physical MAC does.