Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Has the time come to drop NSS?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Claes Jakobsson via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 1 Feb 2022 14:35:16 +0100
> On 1 Feb 2022, at 14:24, Cristian RodrÃguez via curl-library <curl-library_at_lists.haxx.se> wrote:
>
> On Tue, Feb 1, 2022 at 7:28 AM Daniel Stenberg via curl-library
> <curl-library_at_lists.haxx.se> wrote:
>>
>> On Tue, 1 Feb 2022, Daniel Gustafsson via curl-library wrote:
>>
>>> While thats true, that site is also a snapshot from 2008 carrying a warning
>>> that some content may be unchanged since 1998, with NSPR 4.6 cited as the
>>> latest release while a recent NSS requires NSPR 4.32 (4.33 is the latest).
>>> It's not really a substitute for an actual API documentation.
>>
>> In the issue I filed about this problem I was directed to:
>>
>> https://firefox-source-docs.mozilla.org/security/nss/index.html
>>
>> (featuring this lovely warning: "It currently is very deprecated and likely
>> incorrect or broken in many places.")
>>
>> ... which took me to this page:
>> https://firefox-source-docs.mozilla.org/security/nss/legacy/reference/nspr_functions/index.html?highlight=pr_read
>>
>> ... which lead me to a 404 when I pressed that PR_Read link! :-/
>
> It is my belief this library is really only suitable for use within
> the moz ecosystem and not really for anything else.
> At some point openssl had a weird license and its code was on a really
> rough shape.. nowadays the license problem is gone and the code
> quality has improved immensely.
At least ten years ago the PKCS#11 support in NSS was, at least from our extensive use and testing, far superior to the one provided by OpenSSL at the time especially when talking to cryptographic smartcards. If this is not longer the case then dropping NSS would be fine.
/Claes
Date: Tue, 1 Feb 2022 14:35:16 +0100
> On 1 Feb 2022, at 14:24, Cristian RodrÃguez via curl-library <curl-library_at_lists.haxx.se> wrote:
>
> On Tue, Feb 1, 2022 at 7:28 AM Daniel Stenberg via curl-library
> <curl-library_at_lists.haxx.se> wrote:
>>
>> On Tue, 1 Feb 2022, Daniel Gustafsson via curl-library wrote:
>>
>>> While thats true, that site is also a snapshot from 2008 carrying a warning
>>> that some content may be unchanged since 1998, with NSPR 4.6 cited as the
>>> latest release while a recent NSS requires NSPR 4.32 (4.33 is the latest).
>>> It's not really a substitute for an actual API documentation.
>>
>> In the issue I filed about this problem I was directed to:
>>
>> https://firefox-source-docs.mozilla.org/security/nss/index.html
>>
>> (featuring this lovely warning: "It currently is very deprecated and likely
>> incorrect or broken in many places.")
>>
>> ... which took me to this page:
>> https://firefox-source-docs.mozilla.org/security/nss/legacy/reference/nspr_functions/index.html?highlight=pr_read
>>
>> ... which lead me to a 404 when I pressed that PR_Read link! :-/
>
> It is my belief this library is really only suitable for use within
> the moz ecosystem and not really for anything else.
> At some point openssl had a weird license and its code was on a really
> rough shape.. nowadays the license problem is gone and the code
> quality has improved immensely.
At least ten years ago the PKCS#11 support in NSS was, at least from our extensive use and testing, far superior to the one provided by OpenSSL at the time especially when talking to cryptographic smartcards. If this is not longer the case then dropping NSS would be fine.
/Claes
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-02-01