Closed Bug 89281 Opened 23 years ago Closed 23 years ago

Personal Certificate backup or backup all fails to store cert.

Categories

(Core Graveyard :: Security: UI, defect, P1)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
PowerPC
macOS
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
psm2.1

People

(Reporter: david, Assigned: javi)

References

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.2) Gecko/20010702
BuildID:    0000000000

After going through the entire preferences dialogue process (with backup or
backup all) for certificate backup, and entering both the security device and
backup password, nothing is stored in the specified backup file locztion.

Reproducible: Always
Steps to Reproduce:
1.Open Preferences, Privacy and Security, Certificates
2.Click on Manage Certificates
3.Hit return to reveal certificate list (this is a separate bug--the preferences
window cannot be moved or resized out of the way)
4. Highlight own certificate
5. Click Backup or Backup All
6. Enter file name, select storage location
7.Click OK
8. Enter master password
9. Enter backup certificate storage password and confirmation
10. Click OK
11. Click Close

Actual Results:  Preference closes without storing backup certificate.


Expected Results:  Backup certifcate(s) stored.
This was recently fixed, but now depends on bug 89401 to verify the fix.
Status: UNCONFIRMED → NEW
Depends on: 89410
Ever confirmed: true
Summary: Personal Certificate bzckup or backup all fails to store. → Personal Certificate backup or backup all fails to store cert.
t->2.1
->ddrinan
Assignee: ssaux → ddrinan
Priority: -- → P2
Target Milestone: --- → 2.1
Version: 1.01 → 2.0
P1
Priority: P2 → P1
Is this only on MacOS X?
-> javi
Assignee: ddrinan → javi
As of build 22001071905 (Mac OSX) Backup All stores a key file. But when one
tries to restore it, one get "Fails to restore...for some unknown reason."

It may be that the keys are already present in Mozilla, or it may be some other
problem.  Perhaps this should be a new bug--dunno.
QA > petersen
QA Contact: junruh → petersen
adding nsenterprise to all P1, P2 PSM bugs with target milestone of 2.1
Keywords: nsenterprise
add sdagley to cc list.
I just tried this using my build from 8/20 and it the certs were exported just fine.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
On restore it does say "Unknown reasons" and that is because the certs are
already there. (Bad error message I know).

If you restore the .p12 file into a new profile, then it works successfully.
Verified on Mac OSX 9/21
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.0 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.