Home » All CA/Browser Forum Posts » 2025-01-09 Minutes of the Code Signing Certificate Working Group

2025-01-09 Minutes of the Code Signing Certificate Working Group

Attendees

Brianca Martin - (Amazon), Brian Winters - (IdenTrust), Bruce Morton - (Entrust), Corey Bonnell - (DigiCert), Dean Coclin - (DigiCert), Inaba Atsushi - (GlobalSign), Iñigo Barreira - (Sectigo), Kateryna Aleksieieva - (Asseco Data Systems SA (Certum)), Luis Cervantes - (SSL.com), Marco Schambach - (IdenTrust), Martijn Katerbarg - (Sectigo), Nome Huang - (TrustAsia), Rebecca Kelly - (SSL.com), Roberto Quionones - (Intel), Scott Rea - (eMudhra), Thomas Zermeno - (SSL.com), Tim Crawford - (CPA Canada/WebTrust), Trevoli Ponds-White - (Amazon)

Note Well

Martijn read the Note Well,

Approval of prior meeting minutes

The December 12, 2024 minutes were approved.

Max validity of CS certs

Ian was not on the call. Martijn will reach out to Ian.

Dean advise that there have been some questions on the ballot. A concern is that some Subscribers are using tokens and shorter validity periods may be an issue. An alternative would be for Subscribers to use a signing service.

During the meeting, Ian sent an email. Ian will have a proposal before 1 February 2025. Nate will transition in February.

Aligning CSCWG BRs with recent SCWG ballots

A proposal has been created in Github incorporating 5 Server Working Group ballots. Am now looking for two endorsers. Martijn stated he would endorse.

Bruce stated that the effectivity date stated is 15 June 2025, this can change if this is an issue. Regarding pre-sign linting, this was included as a SHOULD, since there are no linters which cover the CSBRs.

Other business

Bruce suggested that we should consider a clean-up ballot. This would make a correction from another ballot, plus remove some past effective dates. This would be a new ballot.

Martijn stated we will need to start working on one certificate type this year.

Next Meeting

January 23, 2025

Latest releases

Server Certificate Requirements
SC095v3: Clean-up 2025 - Apr 2, 2026

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.14 - Ballot SMC016 - May 5, 2026

This ballot maintains consistency between the S/MIME Baseline Requirements and the TLS Baseline Requirements with changes introduced by Ballots SC096 and SC097. Specifically, this ballot: Creates a carve-out of the logging requirements for DNSSEC specifically, stating these are not in scope. For audit purposes, change management logging is able to confirm if the appropriate controls are in effect or not. Sunsets all remaining use of SHA-1 signatures in Certificates and CRLs. It is noted that most uses of SHA-1 signatures are already deprecated by SC097. With this ballot, all unexpired Subordinate CA Certificates issuing S/MIME containing the SHA-1 signature algorithm must be revoked. This proposal does not prohibit the use of SHA-1 to generate issuerKeyHash or issuerNameHash values as currently required by RFC 5019. Includes minor formatting corrections.

Network and Certificate System Security Requirements
Version 2.0.5 (Ballot NS-008) - Jul 9, 2025