Skip to content

DRAFT: Allow "pseudo:" prefix in CN for smime sponsored and individual#156

Open
axel-sws wants to merge 3 commits intodigicert:mainfrom
axel-sws:allow-pseudo-prefix
Open

DRAFT: Allow "pseudo:" prefix in CN for smime sponsored and individual#156
axel-sws wants to merge 3 commits intodigicert:mainfrom
axel-sws:allow-pseudo-prefix

Conversation

@axel-sws
Copy link
Copy Markdown

This merge request adds a "hotfix" for issue #155, allowing "pseudo:" prefix in subject:commonName if it is present along with subject:pseudonym.

I'm sure there is more "frameworky" way of implementing this, especially we might want to emit a NOTICE in case a "pseudo:" prefix is encountered. I'm sharing this hotfix hoping to be useful to you, as we had to implement something we can test against sponsored-multipurpose certificates using pseudonyms.

This certificate has:

 - subject:commonName: "pseudo: some-pseudonym"
 - subject:pseudonym: "some-pseudonym"

Which does not match, as validations enforce an exact match on
commonName / pseudonym.
If subject:commonName is present along with subject:pseudonym, allow
subject:commonName prefixed with "pseudo:" or "Pseudo:", with or
without whitespace after the colon.
Remove the CommonNameValidator error, as "pseudo:" prefix is allowed
by previous commit:

   Allow "pseudo:" prefix in CN for smime sponsored and individual
@CBonnell
Copy link
Copy Markdown
Collaborator

Thanks for submitting this, @axel-sws! The discussion on the SMIME WG call last week indicated that the current SMIME BRs currently don't allow this, but a ballot will be formulated to permit prefixes/suffixes in the CN to indicate that a pseudonym is included.

We can keep this PR open to integrate the amended requirements in the SMIME linter when such a ballot is passed.

@axel-sws axel-sws closed this Oct 6, 2025
@axel-sws axel-sws deleted the allow-pseudo-prefix branch October 6, 2025 09:52
@axel-sws
Copy link
Copy Markdown
Author

axel-sws commented Oct 6, 2025

I accidentally deleted my branch "allow-pseudo-prefix", which automatically closed this pull request.
Fixed by recreating the branch, re-opening.

Apologies for the inconvenience

@axel-sws axel-sws reopened this Oct 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants