News for hackers. Stuff that matters.
Re:Important security vulnerabilities in OpenVPN by vog on Wednesday June 21, 2017 @09:30AM (#14603581)
The LibreSSL fork tries to do exactly that: Although they still provide the original OpenSSL API for existing applications, they add a much simpler and hassle-free API on top of it ("libtls" [1]), with the goal that all applications will be switched part-by-part to the new interface.

[1] https://www.openbsd.org/papers/libtls-fsec-2015/

Re:Important security vulnerabilities in OpenVPN by baby on Wednesday June 21, 2017 @10:07AM (#14603893)
Does it make sense to stop recommending OpenSSL and start recommending LibreSSL now?
Re:Important security vulnerabilities in OpenVPN by wbl on Wednesday June 21, 2017 @11:19AM (#14604522)
Yes. Or tell people to use mebd or s2n or the other one that doesn't allocate. Don't use OpenSSL.
Re:Important security vulnerabilities in OpenVPN by baby on Wednesday June 21, 2017 @02:35PM (#14606659)
BearSSL
Re:Important security vulnerabilities in OpenVPN by vog on Wednesday June 21, 2017 @11:45PM (#14609994)
Yes, if only because LibreSSL is still a working drop-in replacement (which is nice to have as a first step of adoption), and because in LibreSSL they threw away lots of legacy code.

This throwing away of legacy code should not be underestimated. There were quite a lot of recent OpenSSL security issues from which LibreSSL had just a fraction, simply because the vulnerable code is no longer present at all in LibreSSL.