4 ms·
This can be fixed not only with privacy addresses but also with DHCPv6 instead of SLAAC. The use of the MAC in this way was a bad bit of design but it's easily
by api 5y ago
This can be fixed not only with privacy addresses but also with DHCPv6 instead of SLAAC. The use of the MAC in this way was a bad bit of design but it's easily remedied. There is nothing in IPv6 that mandates that addresses be assigned this way. Like IPv4 they can be anything.
I personally like stuff like :feed:cafe:babe:beef or :dead:d00d :).
- yardstick 5y agoI agree they can be fixed, although I disagree that DHCPv6 is the solution given Android doesn't support DHCPv6. In practice most vendors I know of just use privacy addresses by default now for IPv6, at least outside servers, so it's mostly a non-issue but the fact remains it's something not applicable to IPv4. And for quite a while it was an issue, it's just that IPv6 hasn't been popular enough for consumers to care instead of just security people. > There is nothing in IPv6 that mandates that addresses be assigned this way. Like IPv4 they can be anything. Yes but that's nitpicking at the core RFCs vs the many other supporting RFCs. There's no IPv4 RFC for using a MAC in the IP address, whereas there is with IPv6 (rfc2373 from a quick look, maybe others).
- yjftsjthsd-h 5y agoSure, you can fix it, but you have to fix it; with v4 it just wasn't a problem.
- Dagger2 5y agoIt's not really a problem in v6 either. Most OSs ship with privacy extensions enabled.