Home » All CA/Browser Forum Posts » 2023-07-13 Minutes of the Code Signing Certificate Working Group

2023-07-13 Minutes of the Code Signing Certificate Working Group

Attendees

Andrea Holland (VikingCloud), Atsushi INABA (GlobalSign), Corey Bonnell (DigiCert), Dean Coclin (DigiCert), Dimitris Zacharopoulos (HARICA), Inigo Barreira (Sectigo), Mohit Kumar (GlobalSign), Scott Rea (eMudhra), Tim Crawford (BDO/WebTrust)

Minutes

1 item on agenda today (since Bruce and Ian are away) – removal of BR references, and which is the correct version of X.509 to be used. Dimitris to lead discussion.

Ballot: CSC 19
Latest comments from Tim have been cleared, if no other concerns or objections, discussion period will start on Monday (17 July)
No concerns raised over content, but procedural concern raised over discussion being held during summer holiday period
If quorum is not achieved for vote (due to holiday period impact), a new ballot will be submitted with a new number (same content)
Still waiting on feedback from Microsoft in respect to X.509 version
Server WG requires conformance with RFC 5280 which specifically references X.509 2005 version
Requiring latest version of X.509 is as inclusive as possible (since it already include 2005 edits) and should not present an issue

No other business

Next meeting: July 27

Adjourn

Latest releases

Server Certificate Requirements
BRs/2.1.2 SC-080 V3: Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods - Dec 16, 2024

Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contact… (https://github.com/cabforum/servercert/pull/560) Ballot SC-080 V3: “Sunset the use of WHOIS to identify Domain Contacts and relying DCV Methods” (https://github.com/cabforum/servercert/pull/555)

Code Signing Requirements
v3.8 - Aug 5, 2024

What’s Changed CSC-25: Import EV Guidelines to CS Baseline Requirements by @dzacharo in https://github.com/cabforum/code-signing/pull/38 Full Changelog: https://github.com/cabforum/code-signing/compare/v3.7...v3.8

S/MIME Requirements
v1.0.8 - Ballot SMC010 - Dec 23, 2024

This ballot adopts Multi-Perspective Issuance Corroboration (MPIC) for CAs when conducting Email Domain Control Validation (DCV) and Certification Authority Authorization (CAA) checks for S/MIME Certificates. The Ballot adopts the MPIC implementation consistent with the TLS Baseline Requirements. Acknowledging that some S/MIME CAs with no TLS operations may require additional time to deploy MPIC, the Ballot has a Compliance Date of May 15, 2025. Following that date the implementation timeline described in TLS BR section 3.2.2.9 applies. This ballot is proposed by Stephen Davidson (DigiCert) and endorsed by Ashish Dhiman (GlobalSign) and Nicolas Lidzborski (Google).

Network and Certificate System Security Requirements
v2.0 - Ballot NS-003 - Jun 26, 2024

Ballot NS-003: Restructure the NCSSRs in https://github.com/cabforum/netsec/pull/35