292369 - Should CERT_AsciiToName handle a name as: "title=M.D.,generationQualifier=III,SN=CA,OID.2.5.4.65=#130A466963746974696F7573,initials=Q,givenName=John,L=Gaithersburg,O=Test Certificates,C=US"

Status: RESOLVED DUPLICATE of bug 210584

(NSS :: Libraries, defect)

Description

[Hanfei Yu]

From NIST test 4.3.8, a subject name such as
"title=M.D.,generationQualifier=III,SN=CA,OID.2.5.4.65=#130A466963746974696F7573,initials=Q,givenName=John,L=Gaithersburg,O=Test
Certificates,C=US" cannot be converted to X500Name by calling CERT_AsciiToName.
Does NSS support this?

Comment 1

[Hanfei Yu]

It seems to me, this is an incompatible parsing/reconstruct problem:

When CERT_NameToAscii() was called earlier by NSS library to create the
Certificate SubjectName, with unrecognized attribute, it created the form of
OID.x.x.x.x=#<encoded der hex string>. But later with CERT_AsciiToName() call on
the SubjectName:

1) The subsequent call ScanVal() cannot recognize the special case created by
parser, so it skips the value after special character '#' and returns error

2) CERT_ParseRFC1485AVA() doesn't recognize the tag (OID.x.x.x.x) from its
name2kinds table which is a list of hard-coded tag names.

Hope this helps ...

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

Please see bug 210584 for more details.
Also note that many of the "short names" are non-standard.
It would be reasonable for CERT_AsciiToName to accept them,
but not reasonable for CERT_NameToAscii to generate them.

*** This bug has been marked as a duplicate of 210584 ***