|
|
|
|
|
by AnIrishDuck
4902 days ago
|
|
There are currently several schemes for obtaining a full /128 address from a /64. One appends your device's MAC address and some other stuff to the network prefix. This obviously has some privacy implications. The second appends a random number to the /64. This was added specifically to address the privacy concerns of the previous scheme, and does so as well as any easily routable scheme can. While it's obvious under this scheme what network traffic is headed to, it isn't easy to determine which device on that network is going to receive that traffic. Or that device's past network history, if it routinely switches IP addresses. A /64 isn't a person any more than a IPv4 address is a person. It could identify you on your wifi, your phone, your friends phone, your friends laptop, the kind lady downstairs who you lent your wifi password... all it specifies is the destination subnet for communication. If you're the least bit privacy aware, it's not any easier to track your device using IPv6 vs IPv4. edit: IPv6 is arguably harder to track, because autoconfiguration proceeds without a central DHCP server. In order to log IP <=> client mappings, a router would need to listen for all Neighbor Solicitations to outgoing devices, not just add a couple printfs to the DHCP server. |
|