Email should be IA5STRING instead of UTF8STRING about certificatesigningrequest HOT 4 CLOSED

@pheckenlWork thanks for opening an issue! Can you submit a PR along with a reference?

from certificatesigningrequest.

I do not appear to have permission to open a PR from my fork of the project. My fork does have my patch, if you would like to see what I propose.

I discovered this issue, when trying to sign CSRs generated using the library. The easy-rsa CA threw an error on the email field in the CSR. When I dug further with openssl, it reported the same error. These tools all complained that the email should be an IA5STRING. This wikipedia article is probably what I used as a reference while developing the patch, but it has been long enough that my memory could be faulty: https://en.wikipedia.org/wiki/Certificate_signing_request

from certificatesigningrequest.

I do not appear to have permission to open a PR from my fork of the project. My fork does have my patch, if you would like to see what I propose.

I discovered this issue, when trying to sign CSRs generated using the library. The easy-rsa CA threw an error on the email field in the CSR. When I dug further with openssl, it reported the same error. These tools all complained that the email should be an IA5STRING. This wikipedia article is probably what I used as a reference while developing the patch, but it has been long enough that my memory could be faulty: https://en.wikipedia.org/wiki/Certificate_signing_request

You should be able to open a PR here if you forked directly. For some reason if that doesn't work you should be able to open a new PR and copy your changes.

from certificatesigningrequest.

Glad to help. Thanks again for developing this library.

from certificatesigningrequest.