Hacker News Reader

Comment by walrus01 | Hacker News Reader

This is rather overly complicated and should only be used for test domains you do not care about.

Much easier and very effective is to use the apache2 or nginx config file options to manually disable sslv3, tls1.0 and tls 1.1. Permit only TLS 1.2. If you want to, manually specify the preferred order or crypto.

Any modern browser supports TLS 1.2 just fine. I've done this for every httpd I admin and it has had no effect on reachability.

View on HN

How are you measuring the effect on reachability? My companies network filter can't seem to understand cloudflare certs with their 50+ other domain names in there, and so clients can't connect. If you have HSTS on you can't even fall back to http. So without a phone call to IT to our provider, people just aren't going to that site.

That kind of thing seems impossible to measure.

99.5%+ of browser user agents are something released in 2010 and later that understand TLS 1.2 just fine.

But what if it's not enabled? We see traffic from newish IE browsers that have TLS 1.1 and 1.2 turned off. We actually got user complaints that one of our sites stopped working when we turned off TLS 1.0.

I have no idea why they would be set up that way, but it's clearly out there.

Windows 7 does not default to TLS 1.1 and 1.2 enabled.

While this can enabled via GPO, I really wish MS would release a patch that forces these to be on. There is no reason not to at this point.

Maybe when it initially shipped, but unless somebody has been absolutely ignoring all the last 6 years of updates, the version of IE that comes with Win7 is very much TLS1.2 compatible.

Read my post again.

TLS 1.1 & 1.2 are not enabled by default therefore will not work regardless of compatibility. Try it.

Reply on news.ycombinator.com