4 ms·
So what are the options then if OpenSSL isn’t fit for purpose? Is it possible to move wholesale to a different project? Are any of them trying to ease migration
by robin_reala 13y ago
So what are the options then if OpenSSL isn’t fit for purpose? Is it possible to move wholesale to a different project? Are any of them trying to ease migration over from OpenSSL to themselves?
- antocv 13y agoGnuTLS exists. And NSS in mozilla. Probably others too.
- reidrac 13y agocURL makes a nice comparison: http://curl.haxx.se/docs/ssl-compared.html http://curl.haxx.se/docs/ssl-compared.html GnuTLS had its own problems recently (see: http://www.gnutls.org/security.html http://www.gnutls.org/security.html), and regarding NSS... I couldn't find a proper public "security" page for it (eg, release notes for 3.16 point to CVE-2014-1492; but the link to the bugzilla issue is not public), so I don't know. Obviously a good security record doesn't imply things like a good code base, good practices, etc; (although it could).
- recentdarkness 13y agoRegarding the NSS CVE-2014-1492: https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-1492 https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-14... Quote: "The cert_TestHostName function in lib/certdb/certdb.c in the certificate-checking implementation in Mozilla Network Security Services (NSS) before 3.16 accepts a wildcard character that is embedded in an internationalized domain name's U-label, which might allow man-in-the-middle attackers to spoof SSL servers via a crafted certificate." Edit: Added Quote
- reidrac 13y agoThanks, I can look for a CVE myself ;) My point is that having a proper security page is a good practice and I really appreciate it as user.
- sp332 13y agoThat chart is out of date. For example, NSS now supports TLS 1.2 https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations#Protocol_support https://en.wikipedia.org/wiki/Comparison_of_TLS_implementati...
- hoggle 13y agoI always felt like there unfortunately was no proper alternative to libopenssl (might be unfair but it seemed like a somewhat smelly library) but thanks to this event I've now been made aware of all the alternatives. How much more fun/comfortable is NSS/GnuTLS to use in a typical C project in comparison to OpenSSL? Great potential to learn for developers and users alike this heartbleed.
- Arnt 13y agoThere are quite a few alternatives (you may also want to look at matrixssl, polarssl/tropicssl and cryptlib), but if you use one of them, people will report interop problems as bugs in your code. Been there, done that. Sad to say, but I now use openssl.
- doe88 13y agoNot sure which one I'd pick; all of the main libraries seems to either have had very bad issues reported at one point or another or are maybe not used enough to inspire enough conficdence; anyway here is a list https://en.wikipedia.org/wiki/Comparison_of_TLS_Implementations https://en.wikipedia.org/wiki/Comparison_of_TLS_Implementati...
- lazyjones 13y agoPerhaps this task should be moved away from libraries (which in some cases are even statically linked and hard to update) into a well-audited daemon, written in a safe language. Or even into several separate daemons for better protection (each with the least privileges required and minimal interface), for example one for handling keys / signing requests only.
- sharpneli 13y agoAnd then we'd have potential exploits both in the daemon and in the safe language runtime/compiler. There is no silver bullet for this. One just needs to keep on looking for exploits and keep on patching them. However there is a lot that can be improved on OpenSSL side. I hope they change their memory allocation strategy after this.
- lazyjones 13y ago> And then we'd have potential exploits both in the daemon and in the safe language runtime/compiler. Now we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without such privileges, application data will be safe. > One just needs to keep on looking for exploits and keep on patching them. This approach hasn't worked in the past and will not work in the future either. Especially when we start with the existing, desolate and probably thoroughly compromised codebases.
- danielweber 13y agoNow we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without such privileges, application data will be safe. This will prevent the prior vulnerability. Will it prevent the next one? Do you know what it won't make the next vulnerability worse? A year or two ago I had to deal with a bunch of people complaining that the embedded device my team was selling was vulnerable to BEAST, because their scanning tool told them it was. I wrote a long essay for the support team about how BEAST is exploited and it's really hard to do it against a limited purpose control GUI with no publicly routeable address, and this worked for about half the people who complained. For the others we had to turn on RC4, which may have been even worse, but now their tool wasn't complaining at them so they were happy, even though they may have been worse off. Thankfully my old team didn't rush to the new OpenSSL version so they got to avoid the past 48 hours being complete shit for them. There aren't clean answers. Like with financial regulation, what you do to make sure the last thing never happens again may create the next thing.
- riffraff 13y agofedora is apparently trying to consolidate all crypto to NSS https://fedoraproject.org/wiki/FedoraCryptoConsolidation https://fedoraproject.org/wiki/FedoraCryptoConsolidation
- recentdarkness 13y agoThat page has not been changed since May 7th 2013, I am not sure that this is currently still actively pursued. Also I haven't seen this on the proposals for F21
- JetSpiegel 13y agohttps://fedoraproject.org/wiki/Releases/21/ChangeSet#System-wide_crypto_policy https://fedoraproject.org/wiki/Releases/21/ChangeSet#System-...
- recentdarkness 13y agoGood to know, I missed that obviously, but that might be because it wasn't a new proposal ;) I am following the proposal by email only and couldn't recall that one :-)
- Confusion 13y agoPolarSSL is used by the OpenVPN-NL variant of OpenVPN that has a Dutch government 'seal of trust' attached to it. They require you to use OpenVPN-NL (instead of regular OpenVPN) for various purposes. They have issued a statement on their mailinglist that they (of course) were not vulnerable.
- higherpurpose 13y agolibsodium, which is a cross-platform version of Dan Berstein's NaCl.
- ctz 13y agoThis is not a TLS stack.
- naveen99 13y agoI suggest using Wei Dai's http://www.cryptopp.com http://www.cryptopp.com as a new starting point for all low level crypto.