Closed
Bug 51226
Opened 24 years ago
Closed 8 years ago
Backup of whole database to PKCS#12 (or similar file)
Categories
(Core Graveyard :: Security: UI, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: drh, Unassigned)
Details
(Whiteboard: [psm-cert-manager])
The current options for backing up a certificate database only allow personal certificates and their chains to be exported to a PKCS#12 format file. It would be useful if the whole database could be backed up and restored, this would include all certificates, S/MIME capabilities and trust settings. This would help for example when the database became corrupted because currently you lose any added CA certificates (and their trust settings) as well as S/MIME certificates. This would also allow external programs to access the database information in a standard form. If PKCS#12 was used for this then some new attributes would need to be added for trust settings and S/MIME capabilities, but MS for example have already added lots of (AFAIK undocumented) attributes for their own purposes.
Updated•23 years ago
|
Keywords: nsenterprise
Comment 5•23 years ago
|
||
remove nsenterprise We have too many bugs to fix to add new functionality.
Keywords: nsenterprise
Comment 6•23 years ago
|
||
Moving all P3 and P4 bugs targetted to 2.1 to future.
Target Milestone: 2.1 → Future
Updated•23 years ago
|
QA Contact: ckritzer → junruh
Comment 8•22 years ago
|
||
Fixing this bug would also fix bug 155889, which asks for the ability to back up the secret decoder ring key.
Updated•21 years ago
|
QA Contact: junruh → bmartin
Updated•17 years ago
|
QA Contact: bmartin → ui
Updated•14 years ago
|
Assignee: kaie → nobody
Whiteboard: [psm-cert-manager]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•