Problem exporting a backup of certificate with a private key. The password is always wrong.
In the latest build downloaded today - 12/2/18 , the certificate back up feature does not allow for a successful export of the certifate and private key combination.
The password always fails.
I downgraded to 57.0.4 (64-bit) and the export worked.
Tested using a Microsoft CA to generate a user certificate for authentication to load an internal web page.
Toutes les réponses (5)
Should confirm, I am using Windows Server 2016 for CA, and using Windows 10 1709 build.
Firefox 58 has changed to other files and for the certificates a SQLite database named cert9.db is used in combination with pkcs11.txt (previously secmode.db). If the password isn't working then something might have gone wrong with the migration. You can try to remove the newer files (cert9.db and pkcs11.txt), to see if it works better this time.
You can use the button on the "Help -> Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page.
- Help -> Troubleshooting Information -> Profile Directory:
Windows: Show Folder; Linux: Open Directory; Mac: Show in Finder - http://kb.mozillazine.org/Profile_folder_-_Firefox
I just wanted to update you to say that this was a fresh build of Windows 10 patched all the way up to the latest build.
Now I did this on the corporate network but did not use our WSUS server so in theory should have all the latest updates direct from Microsoft, using the very latest Firefox as of yesterday (58).
Therefore, my expectation based upon your previous explanation is that those older .db files do not actually exist because at the time I had not installed any older versions of Firefox.
Thank You
John
is there any solution for the above asked question? i am also facing this "password incorrect" error in firefox 59.x i am using windows 7 64-bit., screenshot is attached here .
Modifié le
Ive just built a new domain, installed a new CA, using Firefox and have once again run into the identical issues I logged above a few months back.
I dont think this issue is resolved at all.