621–630 of 643 posts
Earlier quoted context omitted.
My OS gives me IPv6 privacy addresses out-the-box which rotate every few hours.
The prefix is your globally unique identifier. "Privacy addresses" provide zero privacy.
Earlier quoted context omitted.
Kinda sorta. github.com doesn’t have an IPv6 address. github.io does have an IPv6 address. Indeed, one workaround for getting rate limited when using a carrier NAT with github.com is to have a github.io page and pull data from github.io instead of github.com. Edit: About a decade ago, all of my hosting had full IPv6 support, and I tried to move over to IPv6. However, there was an issue with Letsencrypt certs not vali…
>github.io does have an IPv6 address Are you sure? I don't see it. Name: github.io Addresses: 185.199.111.153 185.199.110.153 185.199.108.153 185.199.109.153
Earlier quoted context omitted.
The prefix is your globally unique identifier. "Privacy addresses" provide zero privacy.
“Privacy addresses” are named because in the beginning, your auto-generated IPv6 would incorporate your hardware MAC address verbatim, and many people consider the MAC address to be PII.
Earlier quoted context omitted.
Hyrum's law. That's how IPv4 is being used in practice. > You can quite easily give each host one, and only one, static IPv6 address, just like with old-style IPv4. You literally CAN NOT. On Android there's no way to put in a static IPv6 or even use stateful DHCPv6.
> You literally CAN NOT. On Android there's no way to put in a static IPv6 or even use stateful DHCPv6. Blame the closed and proprietary Android platform for that; not IPv6.
Manual address input is clumsy because of IPv6 address length, stateless RA is limited and doesn't allow network introspection, stateless DHCP is pointless, stateful DHCP is not supported by the most widely deployed OS. There's also prefix delegation that needs stateful DHCP.
Earlier quoted context omitted.
> You're uniquely tagged and identifiable on every website you visit. Almost every modern OS enables IPv6 privacy extensions, ie address randomization, by default.
The prefix is your globally unique identifier. "Privacy addresses" provide zero privacy.
Earlier quoted context omitted.
The prefix is your globally unique identifier. "Privacy addresses" provide zero privacy.
Just like IPv4, then. Ultimately some part of the address has to identify the physical router.
Earlier quoted context omitted.
Remember that, at one stage, the only two types that were useful were FTP and telnet. HTTP and SSH didn't even exist. Let's not strangle the next big thing that doesn't exist yet before it can even be born, yeah?
The next big thing can happen on IPv6
Earlier quoted context omitted.
Mine does and it works so well that I actually have to turn it off when working from home as a bunch of the third party servers at work doesn't have any support for it.
That sounds more like broken support then. Not having any support at all (i.e. A records or v4 literals only) should just send you to whatever v4 transition technology your ISP offers, no?
If GitHub flipped a switch and enabled IPv6 it would instantly break many of their customers who have configured IP based access controls [1]. If the customer's network supports IPv6, the traffic would switch, and if they haven't added their IPv6 addresses to the policy ... boom everything breaks. This is a tricky problem; providers don't have an easy way to correlate addresses or update policies pro-actively. And cu…
> providers don't have an easy way to correlate addresses Yes, they do. It's called DNSSEC.