Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by alienbaby on Friday November 20, 2026 @03:36AM
(#50571832)
I remember a long time ago reading openssl was dumpster file code quality wise. I guess it was just built that way and never improved.
[ Parent
| on HN ]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by secondcoming on Friday November 20, 2026 @05:23AM
(#50572684)
I wanted to see how OpenSSL handles the x64 instructions to accelerate SHA1 hashing and it turns out the assembly code is generated by a perl script.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by actionfromafar on Friday November 20, 2026 @05:42AM
(#50572836)
That's not automatically bad, in fact it can be better than just inlining the instructions.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by cowlevel on Friday November 20, 2026 @08:09AM
(#50574183)
That's normal, if outdated - you'd use Python in anything written since 2010
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by pseudohadamard on Friday November 20, 2026 @09:07AM
(#50574848)
Assuming you mean x86, that part was originally written around 30 years ago via this funky setup that did MD5 and SHA-1 from the same code. It's not really any kind of example of current practice.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by secondcoming on Friday November 20, 2026 @10:36AM
(#50576277)
No, the SHA-NI instructions