[rfe]Forced cert backup requires two separate backup files for a new cert pair

VERIFIED FIXED

Status

()

P3
enhancement
VERIFIED FIXED
18 years ago
10 years ago

People

(Reporter: cotter, Assigned: javi)

Tracking

1.0 Branch
x86
Windows NT
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [nsbeta3-])

(Reporter)

Description

18 years ago
When forced cert backup is enabled for dual certs, the user needs to back up two 
separate p12 files, one for each cert. This can be confusing.

Proposed solution: When dual certs have been issued, forced backup should create 
a single p12 file. When PSM asks for a password for the combined backup file, it 
should display the version of the Choose Portable Security Password dialog 
that's currently associated with the Backup All button--assuming that the 
warning text about incompatibility with Communiator 4.71 etc. still applies.
(Reporter)

Comment 1

18 years ago
Added nsbeta3 keyword, changed QA to junruh.
Keywords: nsbeta3
QA Contact: lord → nitinp

Comment 2

18 years ago
This is a feature.  Marking nsbeta3- and adding rfe to summary.
Summary: Forced cert backup requires two separate backup files for a new cert pair → [rfe]Forced cert backup requires two separate backup files for a new cert pair
Whiteboard: [nsbeta3-]

Comment 3

18 years ago
setting this bug to New. Triaged bugs should not be Unconfirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

18 years ago
Changing QA contact to nitinp
(Assignee)

Comment 5

18 years ago
Fixed in PSM 1.4
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 6

18 years ago
Verified, but bug 56316 is open "Backed up cert is 0 bytes"
Status: RESOLVED → VERIFIED

Comment 7

16 years ago
[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.
Severity: normal → enhancement

Updated

14 years ago
Component: Security: PSM → Security: PSM
Product: PSM → Core

Updated

10 years ago
Version: psm1.2 → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.