Remove the requirement of having to manually configure a cert for S/Mime

NEW
Unassigned

Status

MailNews Core
Security: S/MIME
--
enhancement
16 years ago
8 years ago

People

(Reporter: kaie, Unassigned)

Tracking

Other Branch

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [psm-smime])

(Reporter)

Description

16 years ago
Communicator did not require to manually configure a certificate for S/Mime. It
simply automatically used the latest certificate available that was issued for
the used email account.

I suggest the S/Mime security preferences could be optional.

By default, the preferences could be set to "automatically choose the encryption
certificate".

A separate option could allow the user to empower the user to explicitly select
the cert, as it is currently required to be done.
(Reporter)

Updated

16 years ago
Severity: normal → enhancement
Target Milestone: --- → Future

Comment 1

15 years ago
Mass reassign ssaux bugs to nobody
Assignee: ssaux → nobody
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

14 years ago
Component: Security: S/MIME → Security: S/MIME
Product: PSM → Core
(Reporter)

Updated

13 years ago
Assignee: nobody → kaie
QA Contact: carosendahl → s.mime

Updated

9 years ago
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
(Reporter)

Updated

8 years ago
Assignee: kaie → nobody
Whiteboard: [psm-smime]
You need to log in before you can comment on or make changes to this bug.