CA/Browser Forum
Home » All CA/Browser Forum Posts » Ballot 22 – RSA 1024 Retirement

Ballot 22 – RSA 1024 Retirement

Ballot 22 – RSA 1024 Retirement (Unanimously Passed)

Motion

Robin Alden made the following motion, and Steve Medin and Moudrick Dadashov endorsed it.

Motion begins

The Guidelines should be amended in accordance with the following erratum.

Erratum begins

Delete Appendix A and replace it with the following.

Appendix A Minimum Cryptographic Algorithm and Key Sizes

  1. Root CA Certificates
Root Certificates whose validity period begins on or before 31 Dec 2010Root Certificates whose validity period begins after 31 Dec 2010
Digest algorithmMD5 (NOT RECOMMENDED),SHA-1SHA-1*, SHA-256, SHA-384 or SHA-512
RSA2048†2048
ECCNIST P-256NIST P-256
  1. Subordinate CA Certificates
Subordinate CA Certificates whose validity period begins on or before 31 Dec 2010Subordinate CA Certificates whose validity period begins after 31 Dec 2010
Digest algorithmSHA-1SHA-1*, SHA-256, SHA-384 or SHA-512
RSA10242048
ECCNIST P-256NIST P-256
  1. Subscriber Certificates
Subscriber Certificates whose validity period ends on or before 31 Dec 2010Subscriber Certificates whose validity period ends after 31 Dec 2010
Digest algorithmSHA-1SHA1*, SHA-256, SHA-384 or SHA-512
RSA10242048
ECCNIST P-256NIST P-256

† A Subscriber Certificate may, in addition, chain to an EV-enabled <2048-bit key RSA root CA certificate.

  • SHA-1 SHOULD be used only until SHA-256 is supported widely by browsers used by a substantial portion of relying parties worldwide.

Erratum ends

Motion ends

The ballot review period comes into effect at 18.00 EST on Monday 15th December, and will close at 18.00 EST on Monday 22nd December. Unless the motion is withdrawn during the review period, the voting period will start immediately thereafter and will close at 18.00 EST on Monday 29th December.

Votes must be cast by ‘reply all’ to this email.

A vote in favour of the motion must indicate a clear ‘yes’ in the response. A vote against must indicate a clear ‘no’ in the response. A vote to abstain must indicate a clear ‘abstain’ in the response. Unclear responses will not be counted.

The latest vote received from any representative of a voting member before the close of the voting period will be counted.

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

Edit this page
The Certification Authority Browser Forum (CA/Browser Forum) is a voluntary gathering of Certificate Issuers and suppliers of Internet browser software and other applications that use certificates (Certificate Consumers).