[Smcwg-public] Presence of pseudonym based on commonName value in legacy profile

Stephen Davidson Stephen.Davidson at digicert.com
Tue Apr 18 00:30:48 UTC 2023


Missed one: the Erratum ballot includes:

*	Clarification of Enterprise RA capabilities in 1.3.2
*	Clarification of Pseudonym in 3.1.1, 3.1.3, and 7.1.4.2.2 (a)
*	Consistency of sub-item numbering style in 4.9.1.1 with other CABF
standards
*	Addition of keyUsages for EdDSA in 7.1.2.3 (e)
*	Clarification of LEI role in 7.1.2.3 (l)
*	Correction for ISO 3166-2 characters in 7.1.4.2.2 (d)
*	Clarification of ETSI audit regime in 8.4

 

 

From: Smcwg-public <smcwg-public-bounces at cabforum.org> On Behalf Of Stephen
Davidson via Smcwg-public
Sent: Monday, April 17, 2023 11:46 AM
To: Christophe Bonjean <christophe.bonjean at globalsign.com>; SMIME
Certificate Working Group <smcwg-public at cabforum.org>
Subject: Re: [Smcwg-public] Presence of pseudonym based on commonName value
in legacy profile

 

Hello:

 

I have added this to the Erratum ballot text.  Thank you Christophe.

https://github.com/srdavidson/smime/commit/fc91ff14449f7d2cdee630e1e5167695b
aa3d186
<https://url.avanan.click/v2/___https:/github.com/srdavidson/smime/commit/fc
91ff14449f7d2cdee630e1e5167695baa3d186___.YXAzOmRpZ2ljZXJ0OmE6bzo5NjI2YzA3MD
I2MWY5NjlkNmIwOTg5NjEwMjJkMTg2ZTo2OjE5NjE6ZWYwMGVhMDkxNTI4Mzc4YzYyMWI0Y2YwMz
hiNzJjNTk3NGZhMDIwNDRjYTY2ZWEzMGEwZGI1NTgwNmVhNDAzNDpoOkY> 

 

So, the Erratum ballot now includes:

*	Clarification of Enterprise RA capabilities in 1.3.2
*	Clarification of Pseudonym in 3.1.1, 3.1.3, and 7.1.4.2.2 (a)
*	Consistency of sub-item numbering style in 4.9.1.1 with other CABF
standards
*	Addition of keyUsages for EdDSA in 7.1.2.3 (e)
*	Clarification of LEI role in 7.1.2.3 (l)
*	Clarification of ETSI audit regime in 8.4

 

Regards, Stephen

 

 

From: Smcwg-public <smcwg-public-bounces at cabforum.org
<mailto:smcwg-public-bounces at cabforum.org> > On Behalf Of Christophe Bonjean
via Smcwg-public
Sent: Wednesday, April 12, 2023 11:56 AM
To: smcwg-public at cabforum.org <mailto:smcwg-public at cabforum.org> 
Subject: Re: [Smcwg-public] Presence of pseudonym based on commonName value
in legacy profile

 

Hi all,

 

I propose the following change to address this:
https://github.com/chrisbn/smime/compare/main...chrisbn:smime:pseudonym-fix
<https://url.avanan.click/v2/___https:/github.com/chrisbn/smime/compare/main
...chrisbn:smime:pseudonym-fix___.YXAzOmRpZ2ljZXJ0OmE6bzoyMmIxYThmMWQ3Mzk4Mm
U2ODQyZDc2NjEzMmQ0NWYwMjo2OmZlMTk6MGE2YmQzOWFiOTk1ODcxMDY5OGRiYTE5MzdjNzRkOW
Q0MjJjMmUxYjAwOTZkNjcyZmI1Y2ZlNGIyZDY3NjU1ZTpoOkY> 

 

Maybe we could include this in the erratum ballot?

 

Christophe

 

From: Christophe Bonjean 
Sent: Friday, February 17, 2023 3:44 PM
To: smcwg-public at cabforum.org <mailto:smcwg-public at cabforum.org> 
Subject: Presence of pseudonym based on commonName value in legacy profile

 

Hi all,

 

I'd like to clarify the presence requirements of the subject:pseudonym
field, in combination with the subject:commonName field.

 

According to section 7.1.4.2.2 "Subject distinguished name fields" the
subject:commonName field can contain the value of the subject:pseudonym
field.

 

Note 2 of 7.1.4.2.5 states: "Legacy Generation profiles MAY omit the
subject:givenName, subject:surname, and subject:pseudonym attributes and
include only the subject:commonName as described in Section 7.1.4.2.2(a)."

 

If the commonName field can contain the values of the pseudonym field, but
the pseudonym field MAY be omitted, this seems a bit conflicting.

 

Perhaps we should refer to "Pseudonym" instead of "subject:pseudonym" as the
permitted values for commonName in 7.1.4.2.2 a?

 


Christophe

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20230418/99c43f88/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5263 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20230418/99c43f88/attachment-0001.p7s>


More information about the Smcwg-public mailing list