Earlier quoted context omitted.
It only took changing two settings in about:config to get FF 26 to 'pass.' security.tls.version.max = 3 security.ssl3.rsa_fips_des_ede3_sha = false
Why is that not set by default?
How's my SSL?
21–30 of 91 posts
Re: How's my SSL?
#22Re: How's my SSL?
#23Re: How's my SSL?
#24Safari 6.1.1 is BAD because it allows TLS 1.0 and there seems to be no way to fix it..
Re: How's my SSL?
#25On the built in browser in CyanogenMod 10.1.3: > Bad: Your client is using TLS 1.0, which is very old, possibly susceptible to the BEAST attack, and doesn't have the best cipher suites available either. Interestingly I get "Probably good" using the Chrome browser on the same phone.
Re: How's my SSL?
#26Excellent! (I mean the site. Not so crazy that FF 26 under OSX 10.9.1 is listed as BAD, but I understand and accept the reasoning.) Hopefully this will spur the various vendors to abandon old, broken protocols and ciphers.
It only took changing two settings in about:config to get FF 26 to 'pass.' security.tls.version.max = 3 security.ssl3.rsa_fips_des_ede3_sha = false
Re: How's my SSL?
#27Excellent! (I mean the site. Not so crazy that FF 26 under OSX 10.9.1 is listed as BAD, but I understand and accept the reasoning.) Hopefully this will spur the various vendors to abandon old, broken protocols and ciphers.
Re: How's my SSL?
#28Excellent! (I mean the site. Not so crazy that FF 26 under OSX 10.9.1 is listed as BAD, but I understand and accept the reasoning.) Hopefully this will spur the various vendors to abandon old, broken protocols and ciphers.
It only took changing two settings in about:config to get FF 26 to 'pass.' security.tls.version.max = 3 security.ssl3.rsa_fips_des_ede3_sha = false
I'm not proposing that this is a risk or that Firefox behaves this way---I have no idea. Does anyone else know?
Re: How's my SSL?
#29And for testing your servers: https://www.ssllabs.com/ssltest/analyze.html
Thanks for that. I'm surprised to find that Apple's OSX Server (Mavericks) ships without TLS 1.1 or 1.2 support. Are these not widely deployed? Or no sense of urgency since 1.0 isn't broken.