Closed
Bug 118855
Opened 23 years ago
Closed 18 years ago
rfc2632 requires that s/mime libraries parse a CRL included in a CMS message.
Categories
(MailNews Core :: Security: S/MIME, enhancement, P4)
Tracking
(Not tracked)
People
(Reporter: ssaux, Unassigned)
References
Details
This bug is for tracking purposes. I doubt that we do that today, and I don't
know of any client that actually sends CRLs along with a signed email, but we
may want to remember it.
Reporter | ||
Updated•23 years ago
|
Severity: normal → enhancement
Priority: -- → P4
Target Milestone: --- → Future
Updated•23 years ago
|
QA Contact: alam → carosendahl
Comment 1•22 years ago
|
||
Mail User Agents may not usually include CRLs on sending, however, this is a
very helpful mechanism to push CRLs to users.
A deployment might decided to reguarly or on demand send out S/Mime messages to
all employees to get them in sync with an updated CRL.
A deployment could install a server script that automatically sends out such an
email message.
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
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•