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

https://www.libressl.org/

Re:OpenSSL Security Advisory [7th February 2023] by colmmacc on Tuesday February 07, 2023 @01:37PM (#34697010)
I love LibreSSL and what they represent, but neither LibreSSL nor BoringSSL target all platforms or compatibility with OpenSSL, which can be a bit of a challenge ... and I don't think LibreSSL is likely to have FIPS certification.

At the AWS cryptography group, we've open-sourced our libcrypto - https://github.com/awslabs/aws-lc - which essentially tries to use the best from Google's BoringSSL, OpenSSL (from 1.1x , not 3.x) , our own code, and formal verification and does target a broad set of platforms and is our FIPS module.

We're at about 95% OpenSSL compatibility right now, it "just works" for a lot of applications, and I expect we'll get near-full compatibility this year as we switch more and more of our own systems to using it internally.

We don't promote it broadly, and it's not intended to compete with OpenSSL - but it's a may be an interesting option for some to consider.

Re:OpenSSL Security Advisory [7th February 2023] by mappu on Tuesday February 07, 2023 @02:26PM (#34697931)
Is your FIPS .dll/.so publicly available?

It's surprisingly hard to get FIPS crypto in Golang on Windows.

Re:OpenSSL Security Advisory [7th February 2023] by flangola7 on Tuesday February 07, 2023 @01:31PM (#34696920)
Why isn't it used more?
Re:OpenSSL Security Advisory [7th February 2023] by wolf550e on Tuesday February 07, 2023 @02:13PM (#34697631)
It's not 100% compatible with existing applications. IIRC Alpine Linux tried to switch and reverted back to openssl twice.
Re:OpenSSL Security Advisory [7th February 2023] by Arnavion on Tuesday February 07, 2023 @02:20PM (#34697785)
Gentoo and OPNsense also switched back (to be precise, stopped supporting both and now just support OpenSSL) for the same reason.
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

Re:OpenSSL Security Advisory [7th February 2023] by dochtman on Tuesday February 07, 2023 @02:41PM (#34698199)
A reminder that rustls exists, and leverages the Rust compiler to make sure no memory safety issues exist in your TLS implementation:

https://github.com/rustls/rustls

Some thoughts on lessons learned from other projects/vulnerabilities:

https://docs.rs/rustls/latest/rustls/manual/index.html

Re:OpenSSL Security Advisory [7th February 2023] by Flocular on Tuesday February 07, 2023 @04:25PM (#34699906)
For cryptography it uses the ring-library which still relies on C-Code in many places. Additionally there is no API-stability (still v0.*) and the last official audit was 3 years ago.

The project has potential but isn't quite ready for prime time yet.

Re:OpenSSL Security Advisory [7th February 2023] by oconnor663 on Tuesday February 07, 2023 @06:25PM (#34701458)
Importantly, that C code (and assembly) is in the guts of crypto primitives. Those tend to be a lot easier to test than higher level X.509 parsing code, which I think is all done in safe Rust.

But for sure, taking a dependency on RusTLS from C code isn't a "boring" choice, and I wouldn't pretend to be confident that that would all go smoothly for a big project.