Open
Bug 209347
Opened 22 years ago
Updated 3 years ago
Obtain S/Mime sender's (prefered) encryption certificate
Categories
(NSS :: Libraries, enhancement, P4)
NSS
Libraries
Tracking
(Not tracked)
NEW
People
(Reporter: KaiE, Unassigned)
Details
This bug requests to implement a new functionality in NSS.
When processing a received S/Mime message, there should be an API to obtain the
sender's encryption certificate - which might be same certificate as the
signature, another certificate with the same subject, or even a completely
different certificate.
See also
http://www.ietf.org/rfc/rfc2633.txt
section 2.5.3 Encryption Key Preference Attribute
The requirement for this came up in the context of bug 209182, which will
require the application to import certificates itself.
Without this function, the application will have to implement the required logic
on its own.
Updated•20 years ago
|
QA Contact: bishakhabanerjee → jason.m.reid
Updated•19 years ago
|
Assignee: wtchang → nobody
QA Contact: jason.m.reid → libraries
Updated•19 years ago
|
Priority: -- → P4
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•