Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by adev_ on Friday November 20, 2026 @02:31AM
(#50571338)
> What's obnoxious is the WG14 standard committee could have at any time in the last 40 years
Or just use bloody C++ that solved that years ago with std::span.
Unfortunately, many C dev prefers whining about "How horribly bloated" C++ is instead of using the part that makes sense.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by Gibbon1 on Friday November 20, 2026 @02:42AM
(#50571408)
There are very few reasons to start a greenfield project in C++ at this point.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by adev_ on Friday November 20, 2026 @02:51AM
(#50571467)
There are plenty of reasons to start a greenfield C++ project in 2026.
Providing C compatible APIs is one of them.
However, I do not see any reasons to start a plain C user space project in 2026. Excepted if you are embedded / kernel dev.
Everything advantage you do have in C (portability, compatibility, memory control).... you have them in Modern C++, but better.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by TuxSH on Friday November 20, 2026 @03:38AM
(#50571843)
> embedded
Nintendo has been writing their OSes (3DS and Switch 1/Switch 2) fully in C++ (microkernel included), so not even this is an excuse to use C over C++.
I swear it's de rigueur in C that if an operation requires 5 parameters to insure the operation is error free than the function shall only take 4 parameters.
Rewriting the function with idiot mode disabled
int EVP_EncodeUpdate(EVP_ENCODE_CTX ctx, buffer_t out, const slice_t in);