Closed
Bug 53127
Opened 26 years ago
Closed 26 years ago
Accept UTF8String encoding for attributes in Names
Categories
(NSS :: Libraries, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
3.0.1
People
(Reporter: thayes0993, Assigned: thayes0993)
Details
Attachments
(1 file)
|
1.15 KB,
patch
|
Details | Diff | Splinter Review |
The library should accept the UTF8String encoding of directory string values
found in X.500 names. This encoding is mandated for certificates created after
2003. It should be added as soon as possible to allow for smooth upgrading of
the PKI infrastructure.
NOTE: we do not need to generate UTF8String (yet).
| Assignee | ||
Comment 1•26 years ago
|
||
Setting target to 3.1 (I know this is the current release). Please see the
attachment for diffs.
Priority: P3 → P2
Target Milestone: --- → 3.1
| Assignee | ||
Comment 2•26 years ago
|
||
Comment 3•26 years ago
|
||
Terry, one question about the patch. The comment
/* Convert 8-bit Latin (ISO 8859-1) to UTF8 */
seems out of place under case SEC_ASN1_T61_STRING.
| Assignee | ||
Comment 4•26 years ago
|
||
The stray comment is indicating the location of changes that need to be made for
a different feature (T61 character handling). Please ignore it.
| Assignee | ||
Updated•26 years ago
|
Version: 3.0 → 3.0.1
| Assignee | ||
Updated•26 years ago
|
Target Milestone: 3.1 → 3.0.1
Version: 3.0.1 → 3.0
| Assignee | ||
Updated•26 years ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Comment 6•26 years ago
|
||
Change is checked in, but I don't know how to QA this in the test suite. I've
built a version of PSM that accepts certificates with this encoding as a
one-time test.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•