News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by sippingabonedry on Thursday November 19, 2026 @10:40PM (#50569857)
I see the OpenBSD guys are all over the PR (deservedly) shitting all over the proposed fixes so I assume LibreSSL may be impacted? Or are they just providing free advice and color commentary?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by collinfunk on Thursday November 19, 2026 @10:44PM (#50569881)
I'm not really involved in OpenSSL, aside from a few tiny changes and commenting on a few things that affected GNU coreutils. However, I have seen Bob, whom I assume you are referring to based on the profile picture, participate in many discussions. I wouldn't infer too much from it.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by sippingabonedry on Thursday November 19, 2026 @10:47PM (#50569901)
Do the projects collaborate closely since the split? My history is admittedly fuzzy.

Sometimes the fix can be worse than the bug. Like patching a hole in the wall.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by wahern on Friday November 20, 2026 @12:30AM (#50570535)
Yes, they collaborate. BoringSSL and libressl especially, which IIRC share some of the same developers. But OpenSSL has it's own priorities and vision, which sometimes (often?) clashes with the sensibilities of the BoringSSL and libressl developers. Because OpenSSL is still the de facto standard bearer and developer target, it can get frustrating for the libressl and BoringSSL developers, especially when they zig and OpenSSL decides to zag.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by bentley on Friday November 20, 2026 @12:46AM (#50570630)
Bob is a member of the Engineering & Standards team at the OpenSSL Corporation.

https://openssl-corporation.org/leadership.html

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by vasco on Friday November 20, 2026 @02:22AM (#50571275)
The fact that those are paid and not volunteer replies make this even wilder
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by bvttf on Thursday November 19, 2026 @10:58PM (#50569967)
I think the second, LibreSSL was forked before OpenSSL v3 and this only impacts OpenSSLv4.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by aaronbwebber on Friday November 20, 2026 @01:54AM (#50571056)
Describing the comments on this PR as "shitting all over the proposed fixes" seems wildly out of proportion? This is direct, productive feedback on a PR that led to a consensus and approval on an appropriate fix in ~a week, we don't need to make the OS process sound worse than it is.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by Ekaros on Friday November 20, 2026 @05:04AM (#50572524)
To me it looked like entirely reasonable discussion. Return one value or return an other value. And which one should be chosen based on what is in general expected. And then also consider what parts of code can this sort of change impact.

I really find sad how far we have gone. Purely technical merits of a fix should always be an open conversation.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by bjoli on Friday November 20, 2026 @02:57AM (#50571512)
Isnit a cultural, maybe: i found bob to be constructive and to the point.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by runiq on Friday November 20, 2026 @05:52AM (#50572907)
Nobody is shitting over anything in that PR thread, please stop catastrophizing.