3 ms·
I wonder if the next step of the browser privacy war will be to generate an IP address for every application or web page where SLAAC is used to prevent IP addre
by jeroenhd 4y ago
I wonder if the next step of the browser privacy war will be to generate an IP address for every application or web page where SLAAC is used to prevent IP address based fingerprinting. With separate IP addresses could come a separate hash table as there will be no other services using that IP, defeating fingerprinting efforts on IPv6. It's not like we're lacking IPv6 address space for this as the /64 provided to an IPv6 network is enormous.
- tinus_hn 4y agoAs if noone will think to combine the /32.
- jeroenhd 4y agoBut that doesn't work, because the port number algorithm won't have collisions between different IP addresses. Sure, they're already combining whole /48 blocks into a single tracking point just like they're combining a /32 IPv4 address, but at least on IPv6 it'll prevent this type of passive monitoring. On IPv4 the fact there's a NAT gateway with its own hashing table for multiple devices will already defeat this this type of tracking most of the time.
- _trampeltier 4y agoI also did think about that and wrote it somewhere here a while ago. A new IPv6 address for eatch tab or so.