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

subject:countryName value when verified country doesn't have an ISO 3166-1 country code #223

Closed
robplee opened this issue Nov 14, 2023 · 1 comment
Labels

Comments

@robplee
Copy link
Contributor

robplee commented Nov 14, 2023

The text for subject:countryName in 7.1.4.2.2.n says that if a Subject's verified country doesn't have an ISO 3166-1 country code then "the CA MAY specify the ISO 3166-1 user-assigned code of XX". Is that the only thing that is permitted or that should be permitted to include as a countryName in this case?

By the current text of the SMIME BRs I don't think there's anything stopping a CA putting the name of the country in the countryName field as long as it's not got an ISO code. The text says the CA MAY do that but that means that they don't have to.

If the Black Panther wanted an SMIME certificate, could a CA issue a certificate containing a subject:countryName attribute with the value "Wakanda"? That is the country that the Black Panther is from, and assuming the CA could be provided with sufficient evidence to meet the standards of verification defined by Section 3.2.3 or 3.2.4, I think the SMIME BRs allow a CA to do this by the current text. Wakanda does not have an ISO 3166-1 country code*, so by the BRs the CA MAY include an attribute with the "XX" code, but (by the current text of the BRs) I don't think they are obliged to if they are including a countryName.

* yes, I did check.

@srdavidson
Copy link
Contributor

See srdavidson@86134be

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