Closed Bug 142749 Opened 23 years ago Closed 23 years ago

Can't import my mail certificate

Categories

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

1.0 Branch
x86
Linux

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: georg.wild, Assigned: ssaux)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0+) Gecko/20020506 BuildID: 2002050621 From web.de I have a mail certificate, which I want to import to mozilla. I tried this in the following manor: 1. Go to Pref/P&S/Certificates 2. Click "Manage Certificates" 3. Import 4. Choose File 5. Enter master&cert-PW Result: "The PKCS#12 Operation failed for unknown reasons!" Well, I don't want to make my certificate publically available; OpenSSL says: openssl pkcs12 <freemail.p12 Enter Import Password: MAC verified OK Bag Attributes localKeyID: <something> subject=/C=DE/ST=Deutschland/L=86356 Neusaess/CN=Georg Wild/Email=georg.wild@web.de issuer= /C=DE/L=D-76227 Karlsruhe/O=WEB.DE AG/OU=TrustCenter CA/CN=WEB.DE TrustCenter Voll-Zertifikate/Email=trust@web.de ... I can find "WEB.DE TrustCenter Voll-Zertifikate" under Certificate Manager/Authorities. Reproducible: Always Well, do you know what happens; is it possible to write a clearer error message?
-> PSM
Assignee: mstoltz → ssaux
Component: Security: General → S/MIME
Product: MailNews → PSM
QA Contact: junruh → carosendahl
Version: other → unspecified
This is happening quite frequently with the Thawte Freemail Certs. I think we need to address this by RTM. Reporter, we have other p12 files that we can reproduce this with, so stay tuned.
Severity: normal → major
Status: UNCONFIRMED → NEW
Component: S/MIME → Client Library
Ever confirmed: true
Priority: -- → P2
QA Contact: carosendahl → junruh
Version: unspecified → 2.3
Wow! I can import my certificate with 2002051621
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Marking the original bug verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm2.3 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.