4 ms·

"Bug"

by bjt2n3904 9y ago

"Bug"

mtgx 9y ago
Windows 10 "privacy".
- yuhong 9y ago
  How many people are using IPv6 in the first place though?
  - jgowdy 9y ago
    Almost 36% of US based Google traffic, and 18-20% of worldwide Google traffic. It’s not exactly tiny anymore. Akamai claims over 40% of US traffic, 46% of Belgium, 36% of India, etc. The old meme that nobody is on IPv6 isn’t true anymore. Almost every major ISP from cable to AT&T has an IPv6 deployment in progress with considerable progress.
  - ggm 9y ago
    Between zero and ninety percent depending on which network provider you are on. Comcast? Seventy percent. Reliance Jio in India? Ninety percent. Fptelecom in Vietnam? Sixteen percent. Telstra in Australia? Forty percent. Sky in the UK eighty percent. .. it depends. (I measure this for my day job, btw)
  - cptskippy 9y ago
    Hasn't it been on by default since 8 or 7? Comcast supports it and it works as well or better than ipv4 for me. I would guess everyone using a managed Comcast Gateway and Windows, or anyone on their Network who enabled it manually is running it by default.
  - deleted 9y ago
    [deleted]
  - noinsight 9y ago
    See for yourself: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- geofft 9y ago
  It's hard to determine meaning from two words, a number, and some scare quotes, but I'll take a wild guess at what you meant anyway. IPv6 privacy addresses are a mechanism to restore the privacy previously provided by NAT on IPv4, i.e., masking which actual device behind the same ISP customer (home or business) is opening a connection. Windows 10 breaking this functionality does not make sense under any reasonable threat model of Microsoft attacking your privacy: privacy addresses do basically nothing for the average home (just like NAT does basically nothing to privacy of outbound connections for the average home), MS has no access to the traffic that would contain a private address unless something else has already gone wrong, and it's easy enough to find your private IP address anyway: https://diafygi.github.io/webrtc-ips/ https://diafygi.github.io/webrtc-ips/ (which works for me in Debian stable, using the packaged version of Firefox and no non-free software).

"Bug"

mtgx 9y ago

Windows 10 "privacy".

yuhong 9y ago
How many people are using IPv6 in the first place though?
- jgowdy 9y ago
  Almost 36% of US based Google traffic, and 18-20% of worldwide Google traffic. It’s not exactly tiny anymore. Akamai claims over 40% of US traffic, 46% of Belgium, 36% of India, etc. The old meme that nobody is on IPv6 isn’t true anymore. Almost every major ISP from cable to AT&T has an IPv6 deployment in progress with considerable progress.
- ggm 9y ago
  Between zero and ninety percent depending on which network provider you are on. Comcast? Seventy percent. Reliance Jio in India? Ninety percent. Fptelecom in Vietnam? Sixteen percent. Telstra in Australia? Forty percent. Sky in the UK eighty percent. .. it depends. (I measure this for my day job, btw)
- cptskippy 9y ago
  Hasn't it been on by default since 8 or 7? Comcast supports it and it works as well or better than ipv4 for me. I would guess everyone using a managed Comcast Gateway and Windows, or anyone on their Network who enabled it manually is running it by default.
- deleted 9y ago
  [deleted]
- noinsight 9y ago
  See for yourself: https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
geofft 9y ago
It's hard to determine meaning from two words, a number, and some scare quotes, but I'll take a wild guess at what you meant anyway. IPv6 privacy addresses are a mechanism to restore the privacy previously provided by NAT on IPv4, i.e., masking which actual device behind the same ISP customer (home or business) is opening a connection. Windows 10 breaking this functionality does not make sense under any reasonable threat model of Microsoft attacking your privacy: privacy addresses do basically nothing for the average home (just like NAT does basically nothing to privacy of outbound connections for the average home), MS has no access to the traffic that would contain a private address unless something else has already gone wrong, and it's easy enough to find your private IP address anyway: https://diafygi.github.io/webrtc-ips/ https://diafygi.github.io/webrtc-ips/ (which works for me in Debian stable, using the packaged version of Firefox and no non-free software).