Closed Bug 129818 Opened 22 years ago Closed 22 years ago

won't import digital sig from p12 file

Categories

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

Other Branch
x86
Windows XP
defect

Tracking

(Not tracked)

VERIFIED FIXED
psm2.2

People

(Reporter: patrick.hendriks+bugzilla, Assigned: ssaux)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9+)
Gecko/20020308
BuildID:    2002030803

exported my digital signature from thawte freemail to p12 file.
Did clean install of Win XP Pro and mozilla (clean profile etc), imported the
p12 file again into mozilla which was confirmed by a "succesfully restored your
security certificate(s) and private key(s)". Still the sign. doesn't display in
the YOUR CERTIFICATES tab. tried reboot etc. 
Received messages from others with digital sigs do show up in the OTHER PEOPLE's
tab.

Reproducible: Always
Steps to Reproduce:
1.export dig sig to p12 file
2.format your hard drive ;)
3.clean install of win xp pro
4.clean install of 2002030803 mozilla
5.import p12 file

Actual Results:  sig is not listed

Expected Results:  that it would be listed
-> PSM
Assignee: mstoltz → ssaux
Component: Security: General → Client Library
Product: MailNews → PSM
Version: other → unspecified
I'm quite able to restore my thawte freemail cert using a p12 on build id 2002031103
Priority: -- → P2
Target Milestone: --- → 2.2
Works for me.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
maybe related to bug 128586?

Also, re-requesting a new certificate doesn't help either. Still the certificate
won't show...

Are you using Thawte as well? Cause Thawte Freemail isn't listed in the CA
listing anymore (it used to be there). Maybe that's causing the problem?



Reporter, can you try a newer build when importing your cert? If that doesn't 
work, can you try a new profile?
tried build 2002040203 (and several other builds since reporting) and for all of
them the "import is succesfull", but the cert nevers shows up and cannot be
selected. Created a new profile, and same thing happens.

From the mozilla mail-news NG i found that other people are also suffering from
this. Dave Roberts wrote on March 21 "I even re-installed 0.9.9 after removing my
cert7.db and key3.db files.  I restored my personal certificates, viewed
the last message of my contact (to import his cert), set all trust
settings for the CA, set all trust settings for the end user cert, and
still I cannot encrypt a message to him, or another "Thawte" user."

My uneducated guess is that Thawte Freemail is no longer listed as a CA. All
problems seem to occur for Thawte Freemail.
You should reopen the bug, if it still doesn't work for you even with the latest
nightlies.
still doesn't work for me on 2002041003.

As a said : other people see similar things (mozilla mail-news Newsgroup)
Dave Roberts (March 21)
Karthik Sheka (April 7)

mabye marked worked for me too soon?
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Reporter, is this a dupe of bug 128409, where SmartCards are in use, though not 
mentioned in this bug?
As of the 20020501, I notice that Thawte Freemail is listed as a builtin CA.

I have imported several full chain P12 files (exported from earlier builds), and
have successfully imported them.

Can you try the 0501 builds with a clean cert/keydb?  Verify that Thawte
Freemail is builtin before attempting the import, and then see if the import
succeeds.

If it still doesn't show up, or you dont see the Thawte Freemail Cert in the
builtin tokens, delete the netscape6/mozilla directory and reinstall mozilla again.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Correction - Thawte Freemail displays as a builtin token on the 20020501 build
after importation of the p12 file.  After shutting down and reentering, the
Freemail CA and intermediary display as being members of the software security
device.

It is curious upon import - the Thawte Freemail CA appears in the CA tab as
trusted to sign email.  Importing a p12 file issued by an internal test CA does
not appear in the CA Tab until I exit Cert Manager and reopen it.  The internal
CA is not marked as trusted.

Why when the Thawte CA Cert is imported it appears as a builtin object token and
is trusted, whereas the internal CA appears on the Software Security Device as
untrusted?  If I don't have either of them in the database to begin with,
shouldn't they both appear on the software security device as untrusted?

Trunk and Branch.
del'ing the cert & key now did the trick for 2002050408 on XP Pro.

Was there a reason that Thawte Freemail was excluded as a CA for a while?
Anyway, thanks Charles. Can i change the resolution to fix or do i need someone
else for that? Ah, what the heck, i'll try and see what happens. If this turns
your computer into a smoking pile or rubble, i apologize.
Status: NEW → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → FIXED
Verified.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.