Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by tptacek on Thursday May 14, 2015 @01:58PM
(#9546520)
Those older clients are actually vulnerable to real cryptographic flaws in TLS.
Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by agwa on Thursday May 14, 2015 @01:59PM
(#9546531)
Which flaw, specifically, would the latest version of Safari be vulnerable to?
Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by tptacek on Thursday May 14, 2015 @02:14PM
(#9546620)
I guess it depends on your confidence in the Lucky 13 patch, right?
Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by agwa on Thursday May 14, 2015 @02:22PM
(#9546670)
Indeed.
And to be clear, I'm not saying we shouldn't be moving away from the CBC ciphers as fast as possible - just that dishing out a B grade for supporting a large number of users is not a good way of accomplishing that.
Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by Panino on Thursday May 14, 2015 @03:04PM
(#9546925)
You and tptacek are both right, so how about the following to combine your positions:
* Grade 'A' requires AES-GCM and ChaCha20Poly1305 * Allow CBC for 'A' iff it's a last resort option * Use nginx equivalent of "ssl_prefer_server_ciphers on;"
CBC would then only be used by clients that don't support AE ciphersuites.
Making the effective top grade a B might also reduce the physiological motivation for improving a seriously bad TLS config. At least in the US, anything less than an A is considered very close to failing these days (it's silly, but it's the reality). Making changes just to get a B isn't nearly as motivational as making changes to get an A.