Re:OpenSSL Security Advisory - 26 Sep 2016
by gbrown_ on Monday September 26, 2016 @10:01AM
(#12581843)
The trouble with this isn't the lack of available options (indeed one may argue there are too many). But rather having everyone agree on something with a common API. Also has anything else seen heavy prolonged production usage?
[ Parent
| on HN ]
Re:OpenSSL Security Advisory - 26 Sep 2016
by aomix on Monday September 26, 2016 @11:26AM
(#12582596)
I've read other people make this point. There are a lot of TLS implementations out there but OpenSSL was so synonymous with SSL/TLS for so long that it became a fundamental building block. If an API could be established that lets the-thing-that-does-TLS become a minor detail that's easily configured we'd all be better off.
Removing the dependency on OpenSSL is going to be a challenging, messy job. OpenBSD has mostly transitioned over to their LibTLS API but even they had difficulty moving some projects over.