Closed
Bug 139637
Opened 23 years ago
Closed 6 years ago
Only matching certs should be allowed in S/Mime configuration
Categories
(MailNews Core :: Security: S/MIME, enhancement)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: carosendahl, Unassigned)
Details
Builds: 20020423 Trunk and Branch
If you have two mail accounts configured, you may use the certificates for
account A in the configuration of Account B.
Example:
Account A: carosendahl@netscape.com
Account B: carosendahl@netscape.net
Certificates are issued to email address for account A, but they may also be
configured in the Mail&Newsgroup Account Settings for Account B as well.
Two problems:
#1) Account B should not even see the certificates for Account A in the
dropdown boxes within the mail account settings
#2) There is no warning to the user that they are about to send a message where
the email address has no correspondence to the certificate being used.
Updated•23 years ago
|
Target Milestone: --- → Future
Comment 1•23 years ago
|
||
Changing summary to make the request more clear.
Severity: normal → enhancement
Summary: Multiple accounts may use same certificate for signing → Only matching certs should be allowed in S/Mime configuration
Comment 3•21 years ago
|
||
Mass change "Future" target milestone to "--" on bugs that now are assigned to
nobody. Those targets reflected the prioritization of past PSM management.
Many of these should be marked invalid or wontfix, I think.
Target Milestone: Future → ---
Updated•18 years ago
|
QA Contact: carosendahl → s.mime
You need to log in
before you can comment on or make changes to this bug.
Description
•