To reproduce: create a new profile. Import a cert (software device) Use backup all delete the cert. Import the file used in the backup all step. Expected: the cert is restored. Actual: Get "Failed to restore your cert for unknown reasons" Javi. Actually, the problem may not be with the backup all functionality but rather with the "delete" then "restore" sequence. I.e., the simplest, minimal test case may be: new profile. import a cert. delete the cert. import the cert again. I'll update the bug to confirm when I restart this instance of the browser.
P1 t->2.1 nsenterprise. The simplest test case is indeed to import a p12, delete the resulting cert, and importing the same p12.
Priority: -- → P1
Target Milestone: --- → 2.1
This is caused by us leaking a reference to an NSS certificate somewhere. It turns out PSM2 doesn't notify when the cert already exists in the db. I'll add code to say "Cert and private key already exist" and I'll track down the cert leak.
Target->future. Adding relnote keyword. This only happens if you delete the cert you just exported and then import it again. This is the kind of thing one would do while testing backup/restore, but not something a normal user is likely to do. Note that the cert can be imported after quitting the application. This can be relnoted. -> rangansen since javi goes on sabbatical.
Assignee: javi → rangansen
Severity: major → normal
Keywords: nsenterprise → relnote
Priority: P1 → P2
Target Milestone: 2.1 → Future
This attached patch will tell the user: "This cert and private key already exists in your database." It won't make the the restore successful, but it's a more useful error message in this case.
*** Bug 99190 has been marked as a duplicate of this bug. ***
WFM with the 9/19 Win2000 trunk build.
Status: NEW → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.