Skip to content
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

Question about a certificate encoding error #202

Open
bioleyl opened this issue Jul 5, 2021 · 1 comment
Open

Question about a certificate encoding error #202

bioleyl opened this issue Jul 5, 2021 · 1 comment
Labels

Comments

@bioleyl
Copy link

bioleyl commented Jul 5, 2021

Hello,

I got that on a DCP:
Certificate Issuer and Subject attributes encoding check. Subject organizationName field encoding should be PrintableString, got UTF8String

I don't really understand the problem here. UTF8 is not "printable"?

Best regards

@remia
Copy link
Collaborator

remia commented Nov 25, 2021

Sorry for the late answer here, quoting the standard SMPTE ST 430-2-2017:

Exactly one instance of the OrganizationName attribute is required in the Subject name and the Issuer name. It shall be a PrintableString. It should be a meaningful (to humans) name of the organization that is providing the root of trust for all certificates in this chain. There may be multiple roots of trust. The OrganizationName in the Issuer field shall match the OrganizationName in the Subject field. This means that the OrganizationName shall be the same in all certificates that chain back to the same root.

While not being an expert in ASN.1 I would say PrintableString is simply more restrictive than the UTF8String type the certificate found in your DCP is using and as such is not following strictly the standard.

I can not say if that will cause issue in the field or not.

@remia remia added the question label Dec 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants