←back to thread

The IPv6 Transition

(www.potaroo.net)
215 points todsacerdoti | 1 comments | | HN request time: 0.292s | source
Show context
TabTwo ◴[] No.41906458[source]
As long as you have enterprise products like zscaler, that do not support IPv6. Or switches and routers that are broken in different ways with every update. Userproperties in Active Directory that are to short to insert an IPv6 address.

Why should any enterprise company move to it? Why should any enterprise (at least) double the cost by having to support two protocols when most problems can be solved by various types of NAT?

replies(1): >>41906713 #
1. sebazzz ◴[] No.41906713[source]
> As long as you have enterprise products like zscaler, that do not support IPv6

ZScaler is a burning piece of privacy-violating garbage that as a developer rather get rid of than have.

Nice for non-IT collegues who were previously protected by the corporate proxy server while working in the office, now work at home or other places, and are prone to scamming and visiting forbidden [by the employer] sites.

As a developer a system-wide MITM SSL-decrypting proxy server is a major pain in the ass. Every runtime of developer tools, python, Node, .NET, Docker, Linux (WSL) flavors, etc have their own way to trust root certificates, and as a web developer you do tend to touch a lot of different tools. Secondly, when you do a bit of devops, you can't even check basic things like checking if a website has the correct (valid) SSL certificate without RDP-ing to some server which doesn't have ZScaler installed.

Sorry for my rant. But I'm not allowed to disable ZScaler - but am forced to live with it.