4 ms·
Luckily I moved everything to openbsd's libressl which is /mostly/ compatible. I wonder if this bug affects them, typically the HIGH's haven't[0] It really fe
by dijit 10y ago
Luckily I moved everything to openbsd's libressl which is /mostly/ compatible.
I wonder if this bug affects them, typically the HIGH's haven't[0]
It really feels like every other week there is a bug in OpenSSL and after following along with the libressl blog I understand why- the code is an absolute mess[1]
[0] http://undeadly.org/cgi?action=article&sid=20150319145126 http://undeadly.org/cgi?action=article&sid=20150319145126
[1] http://opensslrampage.org/page/49 http://opensslrampage.org/page/49
- pawadu 10y agoNot much seems to have happened in LibreSSL since the initial rage-sprint. For now, watch this spot: https://marc.info?l=libressl&r=1&b=201609&w=2 https://marc.info?l=libressl&r=1&b=201609&w=2
- parfe 10y ago>Not much seems to have happened in LibreSSL since the initial rage-sprint. Where did you get that impression? https://github.com/libressl-portable/openbsd/commits/master https://github.com/libressl-portable/openbsd/commits/master shows an actively developed project
- throwaway7767 10y agoThe interesting thing about LibreSSL is that it's got such a halo around it that people just assume it's not vulnerable to any OpenSSL bugs. Practically every OpenSSL bug posted here gets the standard "Luckily LibreSSL isn't affected by this kind of thing" response. On a couple of occasions I've taken the bait and linked to the LibreSSL source to show that the relevant bits are in fact not changed at all, so they were both vulnerable. Not saying LibreSSL isn't doing good stuff, I just wish people would actually check if it's affected before using any opportunity to jump on the let's-hate-on-openssl bandwagon. (I haven't looked into these bugs in the LibreSSL code since I don't have time for it right now, but I'm sure some message is forthcoming).
- OrpheanBeholder 10y agoNo one is claiming that LibreSSL has fixed all the OpenSSL bugs, the parent certainly didn't. LibreSSL has historically been vulnerable to less of the bugs than OpenSSL and, for a long time, none of the sev:high bugs.
- anon1385 10y ago>none of the sev:high bugs. Well it looks like that has just changed: https://marc.info/?l=libressl&m=147454940615412&w=2 https://marc.info/?l=libressl&m=147454940615412&w=2
- Alupis 10y ago> LibreSSL has historically been vulnerable to less of the bugs than OpenSSL and, for a long time, none of the sev:high bugs. You say this like LibreSSL has been out for a long time. It's just barely crossed it's 2 year mark... and for most of it's life, it's difficult to call it "production ready". Coupled with its low adoption rate (really only some select BSD's, and some adventurous linux folks), it's not surprising more vulnerabilities haven't been discovered (yet). The OpenBSD folks do good work, but let's not pretend they are infallible.
- pygy_ 10y ago> On a couple of occasions I've taken the bait and linked to the LibreSSL source to show that the relevant bits are in fact not changed at all, so they were both vulnerable. That's not a bulletproof way to assess bugs in LibreSSL because its authors also removed vulnerabilities from general helpers functions, proactively fixing issues in the code that uses them.
- cm3 10y agoAssuming we stay with a library written in C, a better approach would be for everyone to try to move to what's in BoringSSL, which deliberately removed most stuff, more than LibreSSL. If we still stay with C, Ring would be a good replacement, which is partially/primarily written in Rust. That said, LibreSSL's TLS abstractions look like a welcome improvement if you need a C API.
- gbrown_ 10y ago> a better approach would be for everyone to try to move to what's in BoringSSL Google don't recommend you do this. https://boringssl.googlesource.com/boringssl/ https://boringssl.googlesource.com/boringssl/ BoringSSL is a fork of OpenSSL that is designed to meet Google's needs. Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. > which deliberately removed most stuff, more than LibreSSL LibreSSL has taken fixes from BoringSSL but it has the aim of maintaining API compatibility to the point where most applications using OpenSSL should "just work" for the most part. I've not tried building against BoringSSL but form reading their documentation it seems like the API is very much a moving target.
- cm3 10y agoThat's right, but I know several project maintainers who are looking moving to it because BoringSSL's scope is smaller and is sufficient for their projects' needs. That's why I think the BoringSSL's API status will evolve with time. And Ring is based on it, so... Then there's ocaml-tls which aims to provide a drop-in implementation of the OpenSSL API too. We're finally seeing much activibity, and in that sense, I'm glad that Heartbleed happened, but it should have been earlier :).
- Esau 10y agoQuestion: on LibreSSL systems, is the binary still named openssl? I only ask because I seem to recall OS X having LibreSSL now but I still have a openssl binary.