Ballot 117 – EV Code Signing Guidelines Corrections(passed)
Code Signing Certificate Working Group
Key dates
- Effective date
- 17 Mar 2014 12 years ago
- Voting opened
- 17 Mar 2014 12 years ago
- Voting closed
- 24 Mar 2014 12 years ago
- Discussion opened
- 10 Mar 2014 12 years ago
- Discussion closed
- 17 Mar 2014 12 years ago
Resources
AI Summary
Ballot overview
- Ballot 117 addressed corrections to the EV Code Signing Guidelines.
- The motion said there were two issues to correct:
- Section 9.2.2 needed to clarify that the SAN extension must contain the permanentIdentifier and must not contain a domain name or IP address.
- Section 9.2.3 needed to keep the subject common name required for the subscriber’s legal name in code signing certificates.
- The ballot page states Results: Ballot passed.
- The page also says an updated version was posted on the EV Code Signing page.
Voting and review timeline
- The review period was scheduled to begin at 2200 UTC on Monday, 10 March 2014.
- The review period was scheduled to close at 2200 UTC on Monday, 17 March 2014.
- The voting period was scheduled to start immediately after the review period.
- The voting period was scheduled to close at 2200 UTC on Monday, 24 March 2014.
Normative changes
- Replace section 9.2.2 so that the Subject Alternative Name field:
- must be present,
- must contain the permanentIdentifier specified in Section 9.7,
- must not contain a Domain Name or IP Address.
- Amend section 9.2.3 so that the Subject Common Name field is required and must contain the Subject’s legal name as verified under Section 11.2.
- The motion text says these changes were effective immediately.
Outcome
- The ballot passed with the stated voting results.
- The evidence does not provide an IPR end date or any exclusion notice information.
- Effective date
- 2014-03-17
- Voting opened
- 2014-03-17
- Voting closed
- 2014-03-24
- Discussion opened
- 2014-03-10
- Discussion closed
- 2014-03-17
2014-03-17 — CAs must implement the corrected SAN and Subject Common Name requirements immediately Applies to EV Code Signing Guidelines corrections adopted by this ballot; the motion states the changes are effective immediately
AI-generated from the CABF ballot page. The official CABF article remains the authoritative source.
Excerpt
SearchHome » All CA/Browser Forum Posts » Ballot 117 – EV Code Signing Guidelines Corrections(passed)Ballot 117 – EV Code Signing Guidelines Corrections(passed)Ballot 117 – EV Code Signing Guidelines Corrections Yea: ANF, Certinomis, DigiCert, GlobalSign, Izenpe, Logius PKIoverheid, OpenTrust, QuoVadis, SECOM Trust, SSC, StartCom, Symantec, Trend Micro, Trustis, WoSign, Microsoft, and Mozilla.