← CABF Ballot Browser
Ballot-158
failed
Ballot 158 – Adoption of Code Signing Baseline Requirements
Code Signing Certificate Working Group
Key dates
- Voting opened
- 10 Dec 2015 10 years ago
- Voting closed
- 17 Dec 2015 10 years ago
- Discussion opened
- 03 Dec 2015 10 years ago
- Discussion closed
- 10 Dec 2015 10 years ago
AI Summary
Ballot overview
- Ballot 158 proposed adoption of the Code Signing Baseline Requirements.
- The motion stated that the CA/Browser Forum would adopt the recommendation of the Code Signing Working Group for Version 1.0 of the Baseline Requirements for Code Signing.
- The motion was endorsed by Microsoft, Trend Micro, and OATI.
Voting outcome
- Voting on Ballot 158 closed on 17 December 2015.
- The CA category vote was 17 yes, 1 no, and 3 abstentions.
- The browser category vote was 2 yes, 3 no, and no abstentions.
- The ballot failed.
Timing stated in the ballot text
- The review period was scheduled to commence at 2200 UTC on 3 Dec 2015 and close at 2200 UTC on 10 Dec 2015.
- The voting period was scheduled to start immediately after the review period and close at 2200 UTC on 17 Dec 2015.
- The motion stated that, once adopted, the effective date would be October 1, 2016.
Compliance impact
- Because the ballot failed, the proposed effective date did not take effect.
- Voting opened
- 2015-12-10
- Voting closed
- 2015-12-17
- Discussion opened
- 2015-12-03
- Discussion closed
- 2015-12-10
AI-generated from the CABF ballot page. The official CABF article remains the authoritative source.
Proposers
the Code Signing Working Group and is endorsed by Microsoft, Trend Micro and OATI. Further information on the ballot is in the email message below.
Excerpt
SearchHome » All CA/Browser Forum Posts » Ballot 158 – Adoption of Code Signing Baseline RequirementsBallot 158 – Adoption of Code Signing Baseline RequirementsVoting on Ballot 158 (Code Signing BRs) closed on 17 December 2015. The results are as follows:
View on cabforum.org →
Last fetched 16 hours ago