LibreSSL: The first 30 days, and what the Future Holds
Why Hacker News recommends it
Recommended as a funny, fascinating tour of how bad the OpenSSL code was and what cleanup looks like.
What it is
Bob Beck of OpenBSD gives a BSDCan 2014 talk on the first month of LibreSSL, the OpenSSL fork. He explains why they forked, what they removed, and examples of the problems found in the OpenSSL code base.
Recommended by 3 HN commenters across 3 different months, 2014 to 2022.
What Hacker News said
Recommends ivoras · 2014-05 · on “OpenSSL, OpenSSH and NTP to receive support from Core Infrastructure Initiative”
Anyone interested in details of LibreSSL development can watch the BSDCan talk at [this video] - there really are a LOT of instances of braindamaged code in OpenSSL and a radical repair is pretty much the only thing which will work.
Recommends mrweasel · 2020-05 · on “OpenSSL 3.0”
There is a fascinating and funny talk by Bob Beck from OpenBSD on the first 30 days after forking OpenSSL. One of the things he addresses is the scary code and how is prevents community involvement. He also talks a great deal about all that stuff that's not really relevant anymore and how much they removed from the LibreSSL source code. Apparently the crypto modules are pretty well made according to the OpenBSD developers. LibreSSL: The first 30 days, and what the Future Holds: [this video]
Recommends yakubin · 2022-10 · on “Patch OpenSSL on November 1 to avoid “critical” security vulnerability”
I'd expect higher quality code review from OpenBSD folks (who maintain LibreSSL), compared to OpenSSL. Also, an interesting talk: LibreSSL: The first 30 days, and what the Future Holds from BSDCan: < [this video] >
Cites shagie · 2022-09 · on “Outdated vs. Complete: In defense of apps that don’t need updates”
I am reminded of the libressl - 30 days in report. [this video] Removing support for old versions is a simplification of what needs to be considered. It is a reduction of complexity. If someone is running a PHP version that has been EOLed, it is perfectly reasonable to discontinue support for it in a library - even if new features that weren't available in the EOL'ed version haven't been added yet.