-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
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
KeyPair generation error #62
Comments
I'm having the same problem on iceweasel-6.0.2 and debian squeeze. The first time I ran it with a clean profile I still got: but the second time I got: |
According to https://www.mozilla.org/projects/security/pki/nss/ref/ssl/sslerr.html error -8037 means SEC_ERROR_TOKEN_NOT_LOGGED_IN or "The operation failed because the PKCS#11 token is not logged in." |
Somehow the problem is located in chrome/content/ssl/CertificateManager.js as it fails at generating the keypair using this call: var privateKey = NSS.lib.PK11_GenerateKeyPair(...) EDIT: original version of this comment was stupid, indeed :D |
Do you have a password set for your PSM? |
Yes, this was the "problem" and the reported workaround works for me too. Thanks for the help. |
@sid77 git pull requests gladly accepted. =) Closing this for now as a duplicate of 22. |
I will try, as I spotted another issue connected to the password manager :) |
Convergence is not able to generate its KeyPair, this is the log shown in the console:
...
Loaded!
Settings loaded threshold: majority
Configuring cache...
Generating new ca certificate..
KeyPair generation error: -8037
Initializing error: Error generating keypair! , undefined
...
I removed convergence, disabled every other extension, restarted firefox and installed convergence once again: same error.
Convergence works, though, on a new empty profile.
I am running Firefox 6.0.2 on a Slackware64 13.37.
The text was updated successfully, but these errors were encountered: