Comparison of pseudonym and cn in multipurpose sponsor-validated certs

[romanf]

We run into a problem when creating a new certificate profile of the type multipurpose sponsor-validated:

• we use "pseudo: xxx yyy" for subject:commonName
• and "xxx yyy" for subject:pseudonym

This causes pkilint to fail at https://github.com/cabforum/smime/blob/c80922087427b1368cb8991eaad4128ef8fe52c0/SBR.md?plain=1#L2185 .

I can't seem to find in the S/MIME BR where this check is mandated. Can you help me or change the check?

Thanks
Roman

[CBonnell]

Hi Roman,
I don't see any provision in the SMBRs to allow a "pseudo: " prefix in the CN. My read is that the pseudonym and commonName fields must match (both contain the Pseudonym).

Will you be in on the SMIME WG call in a few hours? We can raise it there and see how to proceed. If changes are needed in the linter, I can get those turned around in a few days.

[romanf]

I can't attend, but Adrian from SwissSign will be in the call and he knows even better than me what's the issue here. :)

[srdavidson]

See also cabforum/smime#278