We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems that if we have a Master Password set in ff, NSS will fail to deploy private key.
The text was updated successfully, but these errors were encountered:
confirm this problem, having a master password set for the "software security device" yields SEC_ERROR_TOKEN_NOT_LOGGED_IN (-8037, cf. http://www.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html ) from generateKeyPair (chrome/content/ssl/CertificateManager.js)
KeyPair generation error: -8037
workaround: unset the password once, restart (keygen succeeds), reset the password. future startups ask for the password and succeed.
Sorry, something went wrong.
Sent pull request #64 which should address this issue.
Finally merged this change.
No branches or pull requests
It seems that if we have a Master Password set in ff, NSS will fail to deploy private key.
The text was updated successfully, but these errors were encountered: