[Smcwg-public] [External Sender] Updates to 3.2.4.1/4 relying on signature for personal vetting

Stephen Davidson Stephen.Davidson at digicert.com
Fri Aug 5 14:56:35 UTC 2022


Hi Pedro

Among the options available for vetting an individual is to rely upon a valid signature created by a cert under a regime like eIDAS.

In our discussions, Certificate Issuer reps requested this as a vetting option.

Regards, Stephen





From: Pedro FUENTES <pfuentes at WISEKEY.COM>
Sent: Friday, August 5, 2022 11:52 AM
To: Stephen Davidson <Stephen.Davidson at digicert.com>; SMIME Certificate Working Group <smcwg-public at cabforum.org>
Cc: Adriano Santoni <adriano.santoni at staff.aruba.it>
Subject: Re: [Smcwg-public] [External Sender] Updates to 3.2.4.1/4 relying on signature for personal vetting



I fail to understand why we mention document signing on a BR specification that is not dealing with such EKU.

BR/Pedro





   Le 5 août 2022 à 16:13, Stephen Davidson via Smcwg-public <smcwg-public at cabforum.org<mailto:smcwg-public at cabforum.org>> a écrit :

   

   I had intended that the sentence “Identity attributes are evidenced by the signing Certificate, not by the content of the signed document” would deal with such situations.  I can amplify that intent.



   “Identity attributes are evidenced by the Subject DN of the personal Certificate used to create the digital signature, not by the content of the signed document.”



   That resolve your concern?





   From: Smcwg-public <smcwg-public-bounces at cabforum.org<mailto:smcwg-public-bounces at cabforum.org>> On Behalf Of Adriano Santoni via Smcwg-public
   Sent: Friday, August 5, 2022 5:02 AM
   To: smcwg-public at cabforum.org<mailto:smcwg-public at cabforum.org>
   Subject: Re: [Smcwg-public] [External Sender] Updates to 3.2.4.1/4 relying on signature for personal vetting



   Hello,

   Regarding section 3.2.4.1 Attribute collection of individual identity, item 4:

   On the subject of reference frameworks for digital signatures, I believe there is a problem that should be solved.

   The AATL framework also includes digital signatures that are not associated with a "personal certificate" (as required by §3.2.4.1) and therefore, in my opinion, should not be accepted. I am referring in particular to the DocuSign remote signature service in which the signatures are (commonly) always made with the same key and relative certificate whose Subject is the DocuSign company itself (and not the person signing the document). I have not spent a lot of time investigating the matter, but my understanding is that the link of the DocuSign signature with the signer is just based on a previous email exchange. An "ID Verification" step is a Premium Feature that the average DocuSign user is not obliged to buy.

   To plug this security hole, I recommend clarifying in the BR that DocuSign signatures are only accepted (if ever) only when made with a /personal certificate/ (i.e., not one issued to DocuSign, but rather to Johh Smith, Arianna Garcia, François Bertrand, Hiroshi Nakamura, ecc.)

   Regards

   Adriano





   Il 05/08/2022 00:06, Stephen Davidson via Smcwg-public ha scritto:

NOTICE: Pay attention - external email - Sender is 010001826ae5b527-8ca45c40-e692-4c53-84fa-5296ec0f43f1-000000 at amazonses.com<mailto:010001826ae5b527-8ca45c40-e692-4c53-84fa-5296ec0f43f1-000000 at amazonses.com>





      Hello:



      Certificate Issuer members of the SMCWG had noted a desire to expand the list of regimes of digital certificates that may be relied upon in personal validation.  It was also suggested by a Certificate Consumer that criteria for evaluating these regimes be described.



      Based on our discussions, I have proposed some text in the draft as follows:



      https://github.com/cabforum/smime/commit/33ce560204eaed4162cb70c919bf9f86ffac90cc



      Thanks to Ashish Dhiman and to Eva Van Steenberge for the help!



      Regards, Stephen






      _______________________________________________
      Smcwg-public mailing list
      Smcwg-public at cabforum.org<mailto:Smcwg-public at cabforum.org>
      https://lists.cabforum.org/mailman/listinfo/smcwg-public

   _______________________________________________
   Smcwg-public mailing list
   Smcwg-public at cabforum.org<mailto:Smcwg-public at cabforum.org>
   https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.cabforum.org_mailman_listinfo_smcwg-2Dpublic&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=-bX5hBm1IdRDykQ-dBR8tsFRCM4v1VXUyG7RZa2WqPY&m=qlmivUJ3oIIfAId8uLbpKycOnVbOAi93yMlNccINSR0&s=y3KFwzRiwwLK3UIGJ_mrW_DZ34fqpiiiTy47fkwQ9lc&e=

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/smcwg-public/attachments/20220805/18b853a9/attachment.html>


More information about the Smcwg-public mailing list