3 ms·
cURL 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:
by reidrac 13y ago
cURL 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...