3 ms·
The OpenSSL strategy seems to be to try to leapfrog LibreSSL in terms of version numbers (which already has released a 2.x branch, hence their 3.x versioning),
by zdw 8y ago
The OpenSSL strategy seems to be to try to leapfrog LibreSSL in terms of version numbers (which already has released a 2.x branch, hence their 3.x versioning), and revise their API, but still have considerable complexity.
The LibreSSL approach was to write a new library and API, libtls, which does away with the substantial configuration complexity in applications: https://man.openbsd.org/tls_init.3 https://man.openbsd.org/tls_init.3
I'd argue that LibreSSL's is the better approach.
- kev009 8y agoIt is supremely unlikely Akamai (via Rich Salz who is leading and has led a lot of post heartbleed fixup) take libressl seriously at all nor do any other large contributing company. People in the FreeBSD community knew libressl would be a flash in the pan given the personalities involved and FreeBSD has legitimate large scale commercial usage.
- gonzo 8y agoOpenVPN also disclaims any interoperability with LibreSSL. "Please note that LibreSSL is not a supported crypto backend. We accept patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if newer versions of LIbreSSL break API compatibility we do not take responsibility to fix that."
- zdw 8y agoSeeing as LibreSSL is shipped by Apple in MacOS and iOS, I'm not sure your userbase size argument holds water.