Remix.run Logo
▲ dcrazy 4 hours ago

For those too young to remember 2014, Heartbleed led to both BoringSSL and LibreSSL being forked from OpenSSL.

▲stock_toaster 2 hours ago | parent | next [-]

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-...

▲b112 an hour ago | parent | prev | next [-]

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.

▲morkalork 3 hours ago | parent | prev [-]

TIL it's 2036

▲wahern 2 hours ago | parent [-]

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.)