News for hackers. Stuff that matters.
Re:OpenSSL Security Advisory [7th February 2023] by traceroute66 on Tuesday February 07, 2023 @01:47PM (#34697170)
> A reminder that LibreSSL exists and has a fraction of the problems OpenSSL does.

Ahem. Cough.

Maybe I should leave this little link here for a patch published today ?

https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x...

Re:OpenSSL Security Advisory [7th February 2023] by lucb1e on Tuesday February 07, 2023 @02:48PM (#34698341)
Going by the patch, that looks like the same bug as OpenSSL fixed. That's seven of the eight bugs not applicable.

But this is just one round of patches, I have no further information or experience on/with LibreSSL or how the features compare. Just saying that one patch release does not mean either secure or insecure software.

Re:OpenSSL Security Advisory [7th February 2023] by brynet on Tuesday February 07, 2023 @03:10PM (#34698712)
Commit message: https://marc.info/?l=openbsd-cvs&m=167578479210650&w=2

> "Release date for this was set to be January 31. Unilaterally pushed back to February 7 by OpenSSL by way of announcement of many completely unrelated embargoed issues, some of which they had been sitting on since July 2020"

Re:OpenSSL Security Advisory [7th February 2023] by g0xA52A2A on Tuesday February 07, 2023 @04:04PM (#34699617)
This exemplifies one of the key reasons OpenBSD forked OpenSSL. For those who haven't seen it I'd recommend this presentation from Bob Beck[1], around the 10 minute mark he recounts fixing issues in the memory allocator which had been reported 4 years prior. Seems there's still a similar backlog sitting behind embargoes?

[1] https://www.youtube.com/watch?v=GnBbhXBDmwU