News for hackers. Stuff that matters.
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.