upvote
And also led to Amazon's s2n-tls and libcrypto being released around 2015 too as I call.

EDIT: found the release announcement - June 2015 - https://aws.amazon.com/blogs/security/introducing-s2n-a-new-...

reply
AWS-LC[0] itself based on BoringSSL, it makes it feel safer for those behind ALBs (but looks like this CVE may not be TLS related).

[0]: https://github.com/aws/aws-lc

Edit: corrected fork to based on, I don't actually know if it was a fork and a repo just says based on

reply
I wonder. Realistically, Boring and Libre haven't taking off. I measure that by most use and default deploys. But with LLMs, we may be entering a new world.

In that world, certainly some projects may be impervious to fixes. We've all seen projects that basically eschew all change, and ignore issue trackers, and are basically dead.

But the ones which still live? Eventually this first wave of LLM derived fixes will get through the old churn. Presumably, code will improve dramatically. If that's so, OpenSSL will become "good code". And the same with old legacy projects which are still hanging around.

Meaning... will legacy simply exist forever? Our two forks above will likely fade away, if openssl's code becomes clean as can be.

reply
We used BoringSSL at Cloudflare. I imagine there’s a lot of usage in places you can’t see despite it not seeing more adoption. One place you can see it is all browsers use it since Chromium bundles it everywhere except Apple but Apple’s OSes use it to underpin their Network.framework which underpins WkWebview so all Apple devices use it.
reply
Seriously, at this point BoringSSL is surely more widely deployed than OpenSSL? A billion Apple devices, plus every Chrome installation?
reply
> all browsers use it since Chromium bundles it

Doesn't Firefox use NSS instead?

reply
BoringSSL is somewhat widely used because Google baked it into their projects (and partially by Microsoft, I believe they made a FIPS variant of it and used it in Go?)

LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform. Plus I will admit that being the first and loud "we will fix openssl" they got linked with some loud PR that showed less understanding of code they mocked than OpenSSL developer who wrote it, and that's really impressive when you consider some of the mocked code fragments were results of developers never reading foundational documentation for a platform

reply
> LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform.

Well put. This is the crux of the issue.

If you ever try to use libreSSL you rub up against so much friction that most projects would hammer out early.

reply
There's LibreSSL portable. It worked better in legacy machines I own, go figure.
reply
TIL it's 2036
reply
To be fair, frustrations with OpenSSL long preceded Heartbleed. Heartbleed was just the final straw for those who forked libressl and BoringSSL.

And to be fair to OpenSSL, it was one of the first widely used crypto libraries, along with Netscape's NSS. Setting aside the reasonablebess of the initial choices, the rapid uptake meant those choices were difficult if not impossible to completely unwind, particularly the style and typing of parameters and error reporting. Even today debates rage about signed vs unsigned, etc, in C and other languages. (But suffice it to say there are still alot of unforced errors, IMO, such as implicit output buffer sizes.)

reply