5 ms·

One may consider Mozilla's NSS library (Netscape invented SSL, "Network Security Services") as an alternative to OpenSSL. It has an compatible API layer (extra

by frik 13y ago

One may consider Mozilla's NSS library (Netscape invented SSL, "Network Security Services") as an alternative to OpenSSL. It has an compatible API layer (extra package), is used by Firefox, (Chrome), OpenOffice and has more sane default settings. Check out the comparison tables: http://en.wikipedia.org/wiki/Comparison_of_TLS_Implementations http://en.wikipedia.org/wiki/Comparison_of_TLS_Implementatio...

gcb0 13y ago
Chrome used NSS on android only because of license or something else... now it uses openssl all around.
- barkingcat 13y ago
  Chrome is planning to move to openssl for everything, doesn't mean it uses openssl "now all around". According to the planning doc linked earlier this week, it might take some time to get openssl into chrome. The Plan is for it to occur over 4 "milestones". I'm not sure how long each milestone will take, but suffice it to say, it's not "now". And it was the other way around. Only Chromium Android used OpenSSL. Everywhere else it used NSS (linux, mac desktop, windows) Quote from https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53pQgNR-DppMYwt9XvE6s/edit?pli=1 https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53... "Currently, Chromium supports two different SSL/cryptographic backends. On Windows, OS X, iOS, Linux, and Chromium OS, Chromium uses NSS. On Android, Chromium uses OpenSSL. " Please check your sources carefully and don't write unfactual information. Especially in the realm of crypto it's important to get the details right. It would be even better if you edited your post so future readers don't have to read my post at all in order to get the correct information.
legulere 13y ago
It seems to be even more overly complex and hard to use (when not using the compatibility layer) than openssl though. The ease of use for programmers is also very important as an error of the application programmer can be as bad as an error in the ssl library.

by frik 13y ago

gcb0 13y ago

Chrome used NSS on android only because of license or something else... now it uses openssl all around.

barkingcat 13y ago
Chrome is planning to move to openssl for everything, doesn't mean it uses openssl "now all around". According to the planning doc linked earlier this week, it might take some time to get openssl into chrome. The Plan is for it to occur over 4 "milestones". I'm not sure how long each milestone will take, but suffice it to say, it's not "now". And it was the other way around. Only Chromium Android used OpenSSL. Everywhere else it used NSS (linux, mac desktop, windows) Quote from https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53pQgNR-DppMYwt9XvE6s/edit?pli=1 https://docs.google.com/document/d/1ML11ZyyMpnAr6clIAwWrXD53... "Currently, Chromium supports two different SSL/cryptographic backends. On Windows, OS X, iOS, Linux, and Chromium OS, Chromium uses NSS. On Android, Chromium uses OpenSSL. " Please check your sources carefully and don't write unfactual information. Especially in the realm of crypto it's important to get the details right. It would be even better if you edited your post so future readers don't have to read my post at all in order to get the correct information.

legulere 13y ago

It seems to be even more overly complex and hard to use (when not using the compatibility layer) than openssl though. The ease of use for programmers is also very important as an error of the application programmer can be as bad as an error in the ssl library.