4 ms·
BoringSSL, wolfSSL, LibreSSL, not to mention the various FIPS options.
by dharmab 3y ago
BoringSSL, wolfSSL, LibreSSL, not to mention the various FIPS options.
- aaronmdjones 3y agoARM mbedTLS is one of my favourites. Excellent documentation.
- TheDong 3y agoI think GnuTLS is probably the second most popular TLS library, after openssl. Though actually, maybe, firefox's NSS is now that I think about it a second more. Firefox is at least some fraction of C-library-based ssl traffic out there. I'll also mentions s2n and rustls-ffi for completeness as C libraries, though the former isn't widely used, and the latter is very experimental still. https://github.com/aws/s2n-tls https://github.com/aws/s2n-tls and https://github.com/rustls/rustls-ffi https://github.com/rustls/rustls-ffi respectively.
- snvzz 3y agowolfSSL is an excellent clean implementation. LibreSSL is the drop-in replacement for openssl that everybody should have embraced back when heartbleed happened.
- rollcat 3y ago> LibreSSL is the drop-in replacement for openssl that everybody should have embraced back when heartbleed happened. 100% and 1000x times this. LibreSSL does have some minor incompatibilities, but those were mostly about removing obscure and very rarely useful APIs that were badly designed in the first place. It was quite likely that if your program used these APIs, it had security issues that OpenSSL couldn't solve with an update. (Usability is security. If it's hard to use correctly, then it's easy to create a security hole.) Remember folks, LibreSSL comes from the same people who made OpenSSH, and that "other" OS that had 2 remote holes in almost 30 years. You already trust them, you maybe just don't know it.
- jmclnx 3y agoI was a bit surprise Linux did not move to LibreSSL when it became stable. IIRC, there was a Linux distro using LibreSSL, but a year or 2 ago the went back to OpenSSL for some reason which I did not fully understand.
- konimex 3y ago> but a year or 2 ago the went back to OpenSSL for some reason which I did not fully understand. That would be Void Linux [1]. One of the reasons iirc, is PEP 644 [2], in which CPython drops support for LibreSSL due to it not being fully compatible with OpenSSL 1.1.1 APIs. [1] https://github.com/void-linux/void-packages/issues/20935 https://github.com/void-linux/void-packages/issues/20935 [2] https://peps.python.org/pep-0644 https://peps.python.org/pep-0644
- throw_a_grenade 3y agoThat was either Void Linux (see sibling comment) or Alpine Linux. You might also have read Gentoo Linux announcement (https://www.gentoo.org/support/news-items/2021-01-05-libressl-support-discontinued.html https://www.gentoo.org/support/news-items/2021-01-05-libress... ); technically doesn't fit your description since Gentoo never "switched" or "went back", but rather supported them simultaneously, and just pulled support for LibreSSL at some point.
- crest 3y agoMost applications switching to LibreSSL should seriously consider to go one step further and check if the libtls can replace their existing libssl usage: https://github.com/bob-beck/libtls/blob/master/TUTORIAL.md https://github.com/bob-beck/libtls/blob/master/TUTORIAL.md.