4 ms·
GnuTLS has a non-crazy well documented API with loads of good quality examples, which is why we chose it for libvirt. (It was impossible for us to understand h
by rwmj 6y ago
GnuTLS has a non-crazy well documented API with loads of good quality examples, which is why we chose it for libvirt. (It was impossible for us to understand how to use OpenSSL for basic stuff like opening a connection at the time we made that choice - I sure hope it's improved now.) The lesson is if you want adoption you need to have a clear API with no foot-guns, lots of examples and documentation.
Also I would dispute that GnuTLS is somehow written by "amateurs". I know people who contribute at Red Hat and they are very much professionals, and experts in math and crypto engineering.
- Conan_Kudo 6y agoThis statement is basically the reason why we use GnuTLS as well. In fact, we've basically universally migrated our applications away from OpenSSL to GnuTLS because it's a much better library to use and ship. Additionally, the licensing for GnuTLS is a lot clearer than OpenSSL's, and that made it easier to understand how we could use it.
- rrdharan 6y agoOpenSSL fixed their licensing issues: https://wiki.openssl.org/index.php/OpenSSL_3.0#License_Change https://wiki.openssl.org/index.php/OpenSSL_3.0#License_Chang...
- Conan_Kudo 6y agoUnfortunately, OpenSSL is only in alpha right now. And they didn't do an LLVM-style exception to resolve the issues with GPLv2 software. And improved licensing doesn't fix the horrible API, nor the lack of discipline to prevent API/ABI repeated breakages within the same version series. We'll see if they do better with this in OpenSSL 3.x...
- viraptor 6y agoIt doesn't seem like a lot of people contribute though: https://github.com/gnutls/gnutls/graphs/contributors https://github.com/gnutls/gnutls/graphs/contributors Seems like a 2-people project, where 1 dropped off, and 2 new devs recently joined.
- rwmj 6y agoBecause there are 2 people who contribute massively more than the others, it's rather hard to see the regular work done by other contributors by looking at the graphs. Also gnutls is "just" an API and a framework for TLS, all the crypto primitives work happens in libgcrypt: https://github.com/gpg/libgcrypt/graphs/contributors https://github.com/gpg/libgcrypt/graphs/contributors EDIT: not libgcrypt, libnettle: https://github.com/gnutls/nettle/graphs/contributors https://github.com/gnutls/nettle/graphs/contributors
- megous 6y agoGnuTLS doesn't use libgcrypt. Or at least it's not required. It uses nettle.
- rwmj 6y agoYes you're completely right, I updated my comment.
- viraptor 6y agoStill, that means if there's any new change, there's maybe one other person to review it in gnutls and ... none in nettle. Seems like if niels-moller makes a mistake, we won't know until a CVE.
- agwa 6y agoYes, a good API with good documentation is important. Fortunately, OpenSSL has improved significantly in the last few years. Unfortunately, I've talked with crypto experts about GnuTLS's bizarre session ticket key rotation system and nobody can figure out what the heck GnuTLS was trying to accomplish with it. It doesn't rotate anything important, and by implementing it they accidentally introduced this critical all-zero key bug. This is the hallmark of amateurs.
- weare138 6y ago>Fortunately, OpenSSL has improved significantly in the last few years. After Heartbleed was discovered. I think it's the TLS specification itself that's the problem. It's ridiculously complex and difficult to implement correctly to the point even the experts struggle with it.