Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by JSR_FDED on Friday November 20, 2026 @12:49AM
(#50570647)
You should be comparing with assembly language, not C#.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by uecker on Friday November 20, 2026 @01:06AM
(#50570768)
One can abstract buffer handling away in C just fine, eliminating all those problems. I don't know why programmers insist on open-coding low-level buffer management.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by eptcyka on Friday November 20, 2026 @01:28AM
(#50570884)
Yes, of course, this isn’t C, this is just another case of people writing C wrong.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by stavros on Friday November 20, 2026 @04:10AM
(#50572087)
Perhaps we could use another language, where it's not so easy (or possible) to write it wrong?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by uecker on Friday November 20, 2026 @11:39AM
(#50577484)
It is also easy to write it wrong.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by pjmlp on Friday November 20, 2026 @02:26AM
(#50571304)
Not even that is usable as excuse, only those that never tried out the systems programming languages that either predated C, or where equally developed during the 1970's outside Bell Labs and UNIX ecosystem.
You could have come with something simpler in PL/I.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by Ono-Sendai on Friday November 20, 2026 @03:46AM
(#50571914)
The proper way to do it is to factor out the length calc into a utility function that the API provides. Also the calculated buffer length is passed in to the function, and an error is returned if it's too small.
I know, I know, C is low level and high performance, but surely in the year of our lord 2026, we could have come out with something simpler.
Horrendous is a strong word, you're right.