4 ms·
It's definitely "best practice" to turn off features you don't need. Who knows, maybe in five years someone will find a bad bug in the implementation of the IPv
by mr_mitm 3y ago
It's definitely "best practice" to turn off features you don't need. Who knows, maybe in five years someone will find a bad bug in the implementation of the IPv6 stack, then you'll be glad you decreased your attack surface.
Not saying this is what you should do, just a common rationalization.
- icedchai 3y agoIt's also "best practice" to learn a new, foundational technology (like IPv6) sooner than later, perhaps less than 20 years after it was first available.
- dilyevsky 3y agoRight and what is better way to learn than deploying random features to prod!
- icedchai 3y agoDid I say they had to deploy it to production? If they deployed it in dev and test environments even a few years ago, they might have some experience deploying it in prod today.
- IntelMiner 3y agoIt's only been ratified since 1998 and available as far back as Windows NT4 Pretty sure that's enough time to test it in development...
- taway1237 3y agoI know IPv6, just don't feel the need to use it. I prefer to have one firewall and public network interface to worry about. I can't disable IPv4 yet, so the logical solution is to disable IPv6.