Closed Bug 724545 Opened 13 years ago Closed 13 years ago

Only one of two imported X.509 certificates is visible

Categories

(Thunderbird :: Security, defect)

10 Branch
x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 278689

People

(Reporter: u434910, Unassigned)

Details

(Keywords: regression)

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.0; rv:10.0) Gecko/20100101 Firefox/10.0 Build ID: 20120129021758 Steps to reproduce: I created a X.509 certificate for each of the two mail accounts I own (private, office), using Firefox. I stored both of them in a .p12 file and imported them successfully in Thunderbird -- afterwards both of them were listed in the "own certificates" tab. In the next step I associated the first certificate successfully with the office mail account. Actual results: When I wanted to associate the second certificate with the private mail account the appropriate certificate was not available in the respective select box (see screen shot). Only the certificate for the office mail account was available. Expected results: The second certificate for the private mail account should have been available as well (this worked fine with previous TB versions).
OS: Windows Vista → Windows 7
is the certificate having issues a valid certificate for email use ?
(In reply to Ludovic Hirlimann [:Usul] from comment #2) > is the certificate having issues a valid certificate for email use ? Both certificates are valid. If I delete one of them the other is available and works fine in every respect (signing, encryption, validity).
Which thunderbird version did it work with?
Keywords: regression
(In reply to Magnus Melin from comment #4) > Which thunderbird version did it work with? It definetely worked with 3.0.
(In reply to Raimund Heid from comment #5) > It definetely worked with 3.0. Most likely, you were using certificates with different subject DNs with Tb 3.0 (which was released in late 2009), so you didn't run into this issue then. I rather doubt that this is a regression - instead it's (yet another) dupe of bug 278689.
(In reply to Kaspar Brand from comment #6) > (In reply to Raimund Heid from comment #5) > > It definetely worked with 3.0. > > Most likely, you were using certificates with different subject DNs with Tb > 3.0 (which was released in late 2009), so you didn't run into this issue > then. > > I rather doubt that this is a regression - instead it's (yet another) dupe > of bug 278689. Confirmed. I have created a third certificate with a different CN and it works as expected. I'd still vote for a fix of bug 278689. Thanks for your help.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: