Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by ivanr on Thursday May 14, 2015 @02:22PM
(#9546671)
I am not completely against de-facto standards, but, in the TLS space, Chacha20/Poly1305 is not one. At this time it's mostly used only by Google/Chrome (AFAIK, no other clients support it); we'd need to see better browser support (multiple organisations) and wider server-side support before we can accept it on the basis of widespread use.
Accepting non-standard crypto is a slippery slope, which is why I'd rather take a very conservative approach.
P.S. You mean RFC 7539, which came out only a couple of days ago. Now we only need another RFC for the use in TLS.
Re:Why your 'A' grade SSL is 'outdated cryptography' on Chrome
by tptacek on Thursday May 14, 2015 @02:32PM
(#9546728)
Why exactly do we need to see other browsers support Chacha20? That's a viewpoint I imagine is shared by zero working crypto engineers; am I wrong?
We need to get away from the idea that it's unfair to recognize superior cryptography merely because it's currently only implemented in Chrome.
The grade either reflects the actual quality of a server's TLS configuration, or it reflects something else.
In any case, it's a moot point here, because ChaCha20/Poly1305 is RFC7593.