Closed Bug 178932 Opened 23 years ago Closed 23 years ago

NSS should properly decode unrecognized AVAs

Categories

(NSS :: Libraries, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 39494

People

(Reporter: bugz, Assigned: wtc)

References

()

Details

NSS does not currently display serialNumber AVAs in a DN (the usual ERR=Unknown AVA comes up). It should.
Morphing bug. serialNumber is not one of the published attribute types in RFC 2253. However, STREET is, I don't believe we support that. In section 2.4, the RFC says unrecognized attribute types should be converted as such: If the AttributeValue is of a type which does not have a string representation defined for it, then it is simply encoded as an octothorpe character ('#' ASCII 35) followed by the hexadecimal representation of each of the bytes of the BER encoding of the X.500 AttributeValue. This form SHOULD be used if the AttributeType is of the dotted-decimal form. example: 1.3.6.1.4.1.1466.0=#04024869,O=Test,C=GB NSS currently returns "ERR=Unknown AVA" when it encounters an unrecognized attriubte type.
Summary: NSS should support X.520 serialNumber AVA → NSS should properly decode unrecognized AVAs
Now that I've morphed the bug, I searched around and found that it is a dupe :) *** This bug has been marked as a duplicate of 39494 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.