If you had privacy concerns about using IPv6 before, they remain, and (presumably) you can still disable it at a systemwide level.
Personally, if you're sophisticated enough to be using a VPN for privacy purposes, you can probably figure out whether or not your given solution supports IPv6.
In addition, I disagree that IPv6 is some sort of abject reduction in privacy. Many households already have a single member, so IPv4 wasn't providing much cover there. And (speaking from some experience) IP addresses aren't the best resource when doing tracking: that's what evercookies and supercookies are for.
No, but IP-based tracking is even easier than many other methods and can be done passively.
The IP address may not be the only identifying piece of information, but IPv6 includes strictly more information that can be used to track you, and it makes it far easier to take advantage of that information. Supercookies are bad, but it takes even less tech sophistication and effort to track someone by IP address than with a supercookie.
> Many households already have a single member, so IPv4 wasn't providing much cover there.
A lot of people sit behind NAT with many members. Much as I hate NAT, it does provide this benefit, if only by accident. IPv6 makes it far easier to disambiguate two users behind the same NAT without having to look at any other bits of information (cookies, UA strings, etc.).
Would it surprise you to learn that some ad networks will actually cross-pollute targeting to the group?
Definitely happens in offices I've worked in.
IPv6 with privacy extensions is just as "private" as NAT would be, and a default-deny firewall is just as secure. How these basic fundamentals of networking have escaped so many supposedly "in the know" people is astounding.
So that means if you have a v4 only VPN provider all IPv6 happily goes over the default route.
This is not surprising to me at all, traffic should follow the default route that is given. If you are privacy conscious you should already know how to disable IPv6... Honestly if it is a bug anywhere it is a bug in the VPN providers that they are not providing IPv6 services for their customers.
Thankfully with OpenVPN IPv6 setup is simple, and while it doesn't provide the privacy extensions like SLAAC (you can only get a single static IPv6 address on the other end of the tunnel), it does allow you to easily tunnel IPv6 traffic as well. I personally do this by pushing 2000::/3 across from my OpenVPN server.
Not really. Since VPNs have many different purposes (privacy is only one, and arguably not even the most common one), disabling all IPv6 traffic whenever a v4-only VPN is enabled may be a bad default for other use cases. In fact, I would be rather surprised if they did this (though pleasantly surprised).