Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by p_l on Friday November 20, 2026 @02:48AM
(#50571443)
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
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by rustyhancock on Friday November 20, 2026 @04:07AM
(#50572064)
> LibreSSL had, IIRC, problem known as OpenBSD-itis. Or to put it bluntly, the developers didn't really care about any other platform.
If you ever try to use libreSSL you rub up against so much friction that most projects would hammer out early.
Well put. This is the crux of the issue.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by anthk on Friday November 20, 2026 @07:45AM
(#50573936)
There's LibreSSL portable. It worked better in legacy machines I own, go figure.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by vlovich123 on Friday November 20, 2026 @11:43AM
(#50577566)
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.
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.