upvote
The forks of OpenSSL are fairly API compatible with upstream, especially if you're not using new and exotic features. So for many projects you can just link to a better maintained fork and be done.
reply
"not breaking userspace" refers to kernel development. OpenSSL is userspace.
reply
Paraphrasing to "don't make breaking API/ABI changes for projects consuming your API/ABI" doesn't materially change a reasonable point. (And I generally agree with that point, although I confess openssl specifically really strains my view)
reply
And this is why the Linux Desktop will never go mainstream. You should never break apps at all, the OS's API surface goes beyond just the kernel.
reply
The Linux desktop is already mainstream. It has been a first class GUI experience for awhile now. Not to mention the endless papercuts in the proprietary OS's stemming from enshittification (Windows generally) or absurdly poor design (hello Finder).
reply
> OpenSSL is userspace.

If only it kept itself to that…

reply
Yeah, we all know users would rather be reliably hacked than unreliably safe.
reply
Users would rather risk getting hacked than have a computer that doesn't boot or doesn't go on the internet. If they preferred the latter they'd unplug it.
reply
Correct. You can plan around reliable insecurity and stay safe. You cannot ensure safety (or security) of unreliable software.
reply