Closed
Bug 368766
Opened 18 years ago
Closed 18 years ago
SIME certificates cannot be assigned to multiple Identify Accounts
Categories
(Thunderbird :: Security, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 252250
People
(Reporter: alpha096, Assigned: dveditz)
Details
Attachments
(1 file)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.2pre) Gecko/20061023 SUSE/2.0.0.1-0.1 Firefox/2.0.0.2pre Build Identifier: version 1.5.0.9 (20060911) An Individual POP3 email account can contain its own S/MIME certificate which is issues and unique for every email account - This functionality is fantastic, however if you use 1 email account which has multiple valid addresses there is NO provision to assign an S/MIME certificate to each of the valid email addresses, which in transit to an ISP use the one single identify. The attached screen shot shows how some major ISP's can make use of a singular identity for storage of multiple addressed email. The email client handles multiple identities very well, however it needs an extra tab apart from PGP signatures to handle S/MIME certificales X .509 Reproducible: Always Steps to Reproduce: 1 Menu >Edit >Account Settings > 2.Select an account with multiple identities 3.Manage Identities > Edit OR create There is no provision for assigning the email address with S/MIME digital certificate. The system forces you to use Multiple identities whenever the user name of a POP3 account is a duplicate. This situation is also possible when in house mail servers are used Actual Results: manage identities should displays only PGP but not S/MIME certificates X .509 Expected Results: There should be an extra tab in manage identities for the assignment if S/MIME certificates X .509 Should provide another tab Before the PGP TAB to enter Digital certificates.
Reporter | ||
Comment 1•18 years ago
|
||
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Comment 3•18 years ago
|
||
Or maybe bug 278549 would have been more appropriate...
You need to log in
before you can comment on or make changes to this bug.
Description
•