-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subject line varies depending on order of fields. #91
Comments
I tried to see this issue.
I checked subject of generated CSR by this commad,
I also tried to parse CSR by perspective of ASN1 by this command,
I could not get an answer yet, though, this issue might just a subject display probrem. |
X509_NAME_print() in crypto/asn1/t_x509.c appears to cause this issue.
|
@Gisleburt Can you close this issue ? |
I asked a question on StackOverflow recently but this may be an actual bug so I thought I'd report it here too.
When creating a CSR, the subject line seems to vary depending on the order of parameters:
For example:
$ openssl req -new -key my.key -out my.csr \ -subj="/C=UK/L=London/O=Org/OU=Unit/CN=my.domain/emailAddress=me@my.domain"
Gives
Which doesn't look right anyway. I don't know if emailAddress is a valid field name, however it is requested when entering the field using the subject prompt in LibreSSL 2.2.7 on OSX, installed via brew, and that will give you the same output.
Further, if you move emailAddress to the beginning of the subject, it then becomes comma seperated:
$ openssl req -new -key my.key -out my.csr \ -subj="/emailAddress=me@my.domain/C=UK/L=London/O=Org/OU=Unit/CN=my.domain"
Not sure how important it is, so long as the subject line doesn't change, the signature will be valid.
The text was updated successfully, but these errors were encountered: