Re:Why TLS 1.3 isn't in browsers yet
by kalleboo on Thursday December 28, 2017 @12:10AM
(#16020442)
The article says "Browsers did not want to re-enable the insecure downgrade and fight the uphill battle of oiling the protocol negotiation joint again for the next half-decade." So I guess the natural solution to that is making the TLS protocol a User-Agent-esque nightmare of compatibility patches and pretending to support something you don't which surely WONT come back to bite them in the ass years down the line...
[ Parent
| on HN ]
1.2 is still secure. This downgrading/oiling is simple and works for all future versions.
TLS is already so complex and ASN.1 makes xml look like c-struct. This begs the question: why would anyone want to make a crypto overly complex ?