Closed Bug 118855 Opened 19 years ago Closed 13 years ago

rfc2632 requires that s/mime libraries parse a CRL included in a CMS message.

Categories

(MailNews Core :: Security: S/MIME, enhancement, P4)

1.0 Branch
x86
Windows 2000
enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 36454

People

(Reporter: ssaux, Unassigned)

References

(Blocks 1 open bug)

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.
Severity: normal → enhancement
Priority: -- → P4
Target Milestone: --- → Future
Blocks: 74157
QA Contact: alam → carosendahl
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.
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 → ---
Product: PSM → Core
QA Contact: carosendahl → s.mime
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 36454
Version: psm2.2 → 1.0 Branch
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.