3 ms·
What would you recommend that isn't derived from the OpenSSL codebase, for C projects that can't use OpenSSL for license reasons? Your recommendation for TLS e
by JoshTriplett 12y ago
What would you recommend that isn't derived from the OpenSSL codebase, for C projects that can't use OpenSSL for license reasons?
Your recommendation for TLS elsewhere in the thread was:
> You should use BoringSLL, LibreSSL, Go crypto/tls, or OpenSSL, in roughly that order.
Three of those are based on OpenSSL, and Go crypto/tls presumably only works with Go.
- tptacek 12y agoPorting to Windows and using schannel. Sorry.
- JoshTriplett 12y agoGuess I'll be sticking to GnuTLS then, if there's no better option available for GPLed projects to use.
- walyne 11y agoAnother option is wolfSSL (https://wolfssl.com/wolfSSL/Home.html https://wolfssl.com/wolfSSL/Home.html) which is GPL-compatible, but also has a commercial license option. They have an OpenSSL compatibility layer, but are not a derivative of OpenSSL. My experience with their software has been very positive, and they have avoided the majority of recent insecurities. Plus they have great support for anyone working on open source projects.