Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-10 > #194689
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | alt.comp.software.firefox, alt.os.linux, comp.mobile.android, alt.internet.wireless, alt.comp.os.windows-10 |
| Subject | Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix |
| Date | 2026-07-21 12:27 +0200 |
| Message-ID | <nc8vsoFc5a2U4@mid.individual.net> (permalink) |
| References | (3 earlier) <113n252$1d5g$1@nnrp.usenet.blueworldhosting.com> <113n5c5$1p2g4$4@dont-email.me> <113nbbn$fu$1@nnrp.usenet.blueworldhosting.com> <nc8qvgFc5a2U2@mid.individual.net> <113nf82$2upc$1@nnrp.usenet.blueworldhosting.com> |
Cross-posted to 5 groups.
On 2026-07-21 11:47, Maria Sophia wrote:
> Carlos E. R. wrote:
>>> With IPv4 + NAT, all devices share one public address, so the ISP can't
>>> tell which device is doing what. With IPv6, each device has its own
>>> globally routable address, so any IPv6 leak identifies both the activity
>>> and the specific device.
>>
>> Ah, no. This is precisely what the RFC 8981 IPv6 privacy extensions are
>> for. The second part of the address rotates, so that nobody outside can
>> track what machine inside of the router is talking.
>>
>> The router knows, but the router is yours and you can erase the logs.
>
> Carlos brings up a good point about RFC 8981 IPv6 privacy extensions where
> we need to distinguish between tracking over time against identifying the
> device right now because there are two parts to an IPv6 address.
> 1. The prefix (this is fixed as it does not rotate under RFC 8981)
> 2. The interface identifier (this is the part RFC 8981 rotates)
>
> Only recently did I learn about RFC 8981 in the Windows ng but from what
> I've researched, AFAIK, RFC 8981 does not hide the device from the ISP.
> a. Therefore, AFAIK, RFC 8981 does not prevent device attribution.
> b. RFC8981 privacy extensions do not prevent VPN bypass.
> c. RFC8981 privacy extensions do not prevent IPv6 leaks.
>
> Given the prefix remains fixed, RFC 8981 cannot hide the device from the
> ISP as RFC 8981 only rotates the interface identifier half of the address.
>
> What remains of IPv6 reveals both the subscriber and the specific device.
> Short term or long term, RFC 8981 does nothing to prevent that prefix leak.
>
> To be clear, RFC 8981 privacy extensions are likely great, but AFAIK, they
> only prevent long-term correlation of activity across different networks.
Long and short. They know what address is talking, but they do not know
what machine inside the house is talking. It is machine XYZW, so what?
That tells them nothing.
Only the router owner knows, if he wants.
On the other hand, the ISP can capture all the traffic from one machine
(not knowing what machine it is actually), and do a traffic analysis on it.
>
> Based on my research (which we discussed in the Windows 10 newsgroup prior)
> privacy extensions rotate only interface identifiers, not prefixes.
>
> That means, if I'm correct, that even with RFC-8981 privacy extensions...
> a. Websites see our IPv6 prefix
> b. Websites know which household the traffic comes from
> c. Websites can correlate all our temporary IPv6 addresses to that prefix
> d. Websites can still identify your home even if the IID rotates
>
Certainly, as this is intentional and an advantage of IPv6, for the
original intentions of Internet design (ie, direct communication person
to person anywhere in the world, without intermediaries). I could send
an email to you without using a public mail server, and I could include
links to files in my computer without hosting them anywhere. For
instance. This is also privacy.
> When RFC 8981 was first suggested on the Windows ng, I thought that was the
> panacea but the prefix is the part that ties all our IPv6 activity to our
> home but RFC 8981 doesn't do anything (as far as I can tell) to the prefix.
>
> As far as I can tell, RFC 8981 does not hide our household identity.
> It only hides our device identity, and even that, only over time. .
>
> Given the prefix remains fixed, even with RFC 8981 privacy extensions,
> the ISP and any IPv6-reachable website can still correlate all IPv6
> activity-short-term and long-term-to the subscriber's household.
>
> Correct me if I'm wrong as I am here to learn so if I'm wrong, say so.
--
Cheers,
Carlos E.R.
ES🇪🇸, EU🇪🇺;
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-20 02:45 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-20 14:03 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 02:43 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 11:18 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 07:36 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 19:28 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 14:32 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Hank Rogers <Hank@nospam.invalid> - 2026-07-21 18:31 -0500
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 15:40 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 18:53 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2026-07-28 00:36 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix David Higton <dave@davehigton.me.uk> - 2026-07-20 20:47 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-20 21:59 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 02:04 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Adam H. Kerman" <ahk@chinet.com> - 2026-07-21 06:37 +0000
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 03:23 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-21 07:59 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 04:41 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 11:03 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 05:47 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 12:27 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 14:10 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 10:53 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 05:19 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix "Carlos E. R." <robin_listas@es.invalid> - 2026-07-21 11:30 +0200
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 06:10 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 19:13 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-22 09:47 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 16:30 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2026-07-22 21:35 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 16:46 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2026-07-23 04:33 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-23 08:12 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-23 16:23 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Oregonian Haruspex <no_email@invalid.invalid> - 2026-07-25 04:58 +0000
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-26 14:25 -0700
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 01:38 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-21 07:51 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-21 03:45 -0400
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Nuno Silva <nunojsilva@invalid.invalid> - 2026-07-22 09:37 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-24 11:36 -0700
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2026-07-22 21:32 +0100
Re: PSA: IPv6 browser privacy leaks are caused by the host yet there's a simple fix Maria Sophia <mariasophia@comprehension.com> - 2026-07-22 16:54 -0400
csiph-web