News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by m00dy on Thursday November 19, 2026 @10:07PM (#50569670)
>>I am really worried about the negative return value being added. Existing third party callers might not be ready to handle this correctly (i.e. if they cast the return to size_t without checking). Could we instead return 0? (In all the added error returns in this PR.)

Rust fixes it.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by sippingabonedry on Thursday November 19, 2026 @10:58PM (#50569968)
Be sure to let us know when your equivalent Rust crypto library is available.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by m00dy on Thursday November 19, 2026 @11:00PM (#50569986)
we don't need many crypto libraries, maybe just one for the whole world, written in Rust and then all functions are math-proofed.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by td521534f12 on Thursday November 19, 2026 @11:04PM (#50570014)
You'd probably need a second one for FIPS.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by staplehorse6553 on Friday November 20, 2026 @01:14AM (#50570804)
Does the alpha-stage WIP code you call 'Rust' compile for 32-bit yet? No? Ok.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by _ache_ on Friday November 20, 2026 @01:42AM (#50570981)
It's not just "math-proofed". You need a lot more to be a crypto library.

Like time-constant, and it's hard to be time-constant in a performance optimised language like Rust. LLVM is doing some magic, and you don't want any magic in a crypto library.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by uecker on Friday November 20, 2026 @02:02AM (#50571107)
A crypto library written in Rust would not be available everywhere, so can not be the only one. And if you formally verify the code, you can also formally verify that it is memory safe, so there is not much point to have it in Rust. Crypto has properties which may be difficult to verify though.

If you want a safe interface that does not require passing random sizes around in extra arguments, this can also be done in C.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by m00dy on Friday November 20, 2026 @04:21AM (#50572188)
it's too late for C/C++ developers.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by anthk on Friday November 20, 2026 @06:13AM (#50573090)
Rust and C developer there. C++ it's an unrelated beast, don't mix C99 users with these. On C, I compiled Gplaces (A barebones Gemini -protocol- client with Clang hardening CFLAGS and I linked it against BoehmGC. That in 32 bit.

On Rust, it's pure love in 64 bit, I acknowledge that (I use Cosmic DE with Pop!_OS so I can relate) and evcode it's my main IDE, Crabcraft being second. But compiling 'simple' TUI tools on Rust it's impossible on 32 bit, even with ZRAM and a total of 1.5GB of RAM.

If you want half-secure TUI tools on 32 bit Golang it's a saner option than C/C++, for instance AERC can be safer than Mutt to read email, even under a Maildir mailbox and email fetched/sent with isync/msmtp.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cyberax on Thursday November 19, 2026 @11:40PM (#50570254)
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by jo-m on Friday November 20, 2026 @02:35AM (#50571367)
If I am not mistaken, the default backend is aws-lc [1] which is... a C library (still better than having the frontend in C as well, though).

Meanwhile, ring [2] carries an explicit disclaimer of "This is an experiment".

[1] https://github.com/aws/aws-lc

[2] https://github.com/briansmith/ring

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by cyberax on Friday November 20, 2026 @03:15AM (#50571653)
You can also use a formally proven https://github.com/ctz/graviola/
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by the8472 on Friday November 20, 2026 @07:41AM (#50573885)
[delayed]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by bjoli on Friday November 20, 2026 @02:50AM (#50571461)
Sometimes I like to think of how little performance would be lost and how much would be gained by just collectively deciding to use Option/Result instead of sentinel values.

Things like the dumb (not like I'm any individual being dumb. Just collective accumulated stupidity) a*hole vulnerability some weeks ago. That wasn't even performance sensitive.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by layer8 on Friday November 20, 2026 @04:58AM (#50572481)
Rust does not fix existing third party callers.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by m00dy on Friday November 20, 2026 @09:38AM (#50575238)
yes, it does. Please refer Rust's return types
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by layer8 on Friday November 20, 2026 @09:57AM (#50575552)
Existing third party callers don't use Rust, so Rust's return types can't possibly help here.