3 ms·
Probably because once you wrap your code around one SSL stack it's hard to migrate it to another. So you stick to the one you use first. OpenSSL, for instance,
by jerf 11y ago
Probably because once you wrap your code around one SSL stack it's hard to migrate it to another. So you stick to the one you use first. OpenSSL, for instance, isn't just an SSL library... since C has no standardized "stream" functionality, it's a whole big generic streaming library with pluggable modules for various streams and the ability to write your own... once you're stuck to that you can get stuck pretty hard if you don't properly wrap it with abstraction, which C is not, ahhh... let's say it's not really the best at that sort of thing anymore, which is of course partially because every language since C has known that it needs to be better than C at this to even be considered by anybody.
- glass- 11y agoLibreSSL is a drop-in replacement for OpenSSL.
- ams6110 11y agoWell that's the intention... is it really in practice? They have deliberately removed a lot of support for rare architectures and features. Distributions such as CentOS/RHEL which are focused on stability are not going to replace OpenSSL in any existing releases.
- technion 11y agoI can confirm that it currently just "drops in" when linked against nginx. This initially took a few small patches, but these have been merged into LibreSSL mainline. I've been testing this against each release for some time and I'm very happy with it.
- richm44 11y agoIt /was/ a drop in replacement for a single point in time but it isn't if you make use of any of the recent improvements openssl has added. For example auto selection of DH/ECDH primes and curves. Note that recently a big clean up of the openssl codebase has taken place so openssl master no longer exposes the internals of structs etc. meaning it's both more auditable and more maintainable. This code is not yet released however.