[Bug 1960736] Re: Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly ( NSS error code: -8018 )

Bug Watch Updater 1960736 at bugs.launchpad.net
Tue Mar 28 20:01:48 UTC 2023

Launchpad has imported 2 comments from the remote bug at

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at

On 2023-03-04T16:42:51+00:00 Bartłomiej Żogała wrote:

Steps to reproduce:

I've faced an issue with all browsers relying in libnss refusing ever X.509 certificate. I've hard time to debug it through months due to not enough information returned from libnss. It was in detail described here:

Actual results:

Root issue is that libnss returned [23391:23426:0213/133531.202486:ERROR:nss_util.cc(286)] After loading Root Certs, loaded==false: NSS error code: -8018
In my case the root cause was poor quality code written by local government agency known for infringing LGPG licence. The configuration change was deployed when installing their PKCS#11 related software and lack of proper debug from Libnss cause I was not able to connect cause and the effect.

Expected results:

Instead of displaying code which couldn't be googled NSS should return
full human readable error name ' SEC_ERROR_UNKNOWN_PKCS11_ERROR' - in
way it does for other errors of same kind.

Reply at:

On 2023-03-07T20:01:34+00:00 Dkeeler wrote:

This is a bug in Chromium, not NSS. You can file a bug here:

Reply at:

** Changed in: nss
       Status: Unknown => Invalid

You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to NSS.

  Libnss3 doesn't log SEC_ERROR_UNKNOWN_PKCS11_ERROR properly  ( NSS
  error code: -8018 )

To manage notifications about this bug go to:

More information about the Ubuntu-mozillateam-bugs mailing list