3 ms·
Sure, let's continue to reward incompetence by further funding openssl. In a sane world, everybody would have switched to libressl ages ago.
by snvzz 7y ago
Sure, let's continue to reward incompetence by further funding openssl.
In a sane world, everybody would have switched to libressl ages ago.
- mlindner 7y agoLibreSSL has all of the same problems as OpenSSL. It's just a fork from an earlier point in time before OpenSSL did it's big rewrite that came with OpenSSL 1.1.1.
- vladsanchez 7y agoI gather that LibreSSL has an (unintended) OpenSSL dependency? "LibreSSL is composed of four parts: - The openssl(1) utility, which provides tools for managing keys, certificates, etc. - libcrypto: a library of cryptography fundamentals - libssl: a TLS library, backwards-compatible with OpenSSL - libtls: a new TLS library, designed to make it easier to write foolproof application" :shrug:
- notaplumber 7y agoNo, LibreSSL is a fork of OpenSSL that predates this vulnerability, it even predates the OpenSSL 1.1.x API break (some compatibility has since been added), and has an entirely separate and new TLS 1.3 implementation. https://www.openbsd.org/papers/bsdcan2019-tls13.pdf https://www.openbsd.org/papers/bsdcan2019-tls13.pdf (video: https://www.youtube.com/watch?v=MCVIBwGOwNY https://www.youtube.com/watch?v=MCVIBwGOwNY) It maintains source compatibility with OpenSSL at an API and command-line level (e.g. openssl(1) utility). LibreSSL cannot copy code from later versions of OpenSSL as they relicensed it under the Apache 2.0 license.
- pnako 7y agoThe few who switched to LibreSSL actually switched back to OpenSSL (Alpine, HardenedBSD). Void is considering switching back too: https://github.com/void-linux/void-packages/issues/20935 https://github.com/void-linux/void-packages/issues/20935
- ccktlmazeltov 7y agoTheir logic is a bit weird to me, I would definitely choose a fork from professional that re-write everything with a security perspective, over a bad library trying to be hardened .
- mlindner 7y agoLibreSSL did not rewrite everything... Look at the code, most of it's identical to what's in OpenSSL. It's a fork, not a rewrite.
- CameronNemo 7y agoThe Void conundrum is that most software does not support LibreSSL's APIs, and that is especially rough because Void is rolling release. OpenBSD does not write patches for the latest Qt release, so people with little crypto experience have to write those patches.
- notaplumber 7y agoWhich is a bizarre statement, all ports development happens on the OpenBSD -current branch, which is effectively a rolling release for developers/users running snapshots. All of those projects that switched were simply expecting LibreSSL/OpenBSD to upstream support, when it hasn't got nearly the same numbers of developers. Also, there were other problems with updating Qt on OpenBSD, but that was resolved. It is maintained by a single developer. https://marc.info/?l=openbsd-ports-cvs&m=158411843726544&w=2 https://marc.info/?l=openbsd-ports-cvs&m=158411843726544&w=2
- CameronNemo 7y ago>rolling release for developers/users running snapshots Well Void is far more on edge than OpenBSD -current. >there were other problems with updating Qt on OpenBSD, but that was resolved They are still trailing us. https://github.com/void-linux/void-packages/pull/15310 https://github.com/void-linux/void-packages/pull/15310