← CABF Ballot Browser
Ballot-132 passed

Ballot 132 – EV Code Signing Timestamp Validity Period (passed)

Code Signing Certificate Working Group

Key dates

Voting opened
09 Sep 2014 11 years ago
Voting closed
16 Sep 2014 11 years ago
Discussion opened
02 Sep 2014 11 years ago
Discussion closed
09 Sep 2014 11 years ago

AI Summary

Generated 2026-06-23 21:27 UTC

Ballot overview

  • Ballot 132, EV Code Signing Timestamp Validity Period, amended the EV Code Signing Guidelines.
  • The motion replaced one hundred and twenty three months with one hundred and thirty five months in Sections 8.2.1 and 9.4, in three places in each section.
  • The ballot text says the change was intended to align TSA-related validity periods across uses and to extend the period for automatic validation of time-stamped code and other objects.

What changed

  • In Section 8.2.1, the text was revised so that a code signature may be treated as valid for up to one hundred and thirty five months by the Timestamp method or the Signing Authority method.
  • Under the Timestamp method, the EV Timestamp Authority certificate may be up to one hundred and thirty five months in the future.
  • Under the Signing Authority method, the Signing Authority certificate may be up to one hundred and thirty five months in the future.
  • In Section 9.4, the maximum validity period for EV Timestamp Certificates and EV Code Signing Certificates issued to Signing Authorities was revised to one hundred and thirty five months.
  • The validity period for an EV Code Signing Certificate issued to a Subscriber remained not to exceed thirty-nine months.

Voting and status

  • Voting on the ballot closed on 16 September 2014.
  • The page states there were no votes against and no abstentions.
  • The page explicitly says the ballot passed.

Dates

  • The review period was scheduled to commence at 2100 UTC on Tuesday, 2 September 2014 and close at 2100 UTC on Tuesday, 9 September 2014.
  • The voting period was scheduled to start immediately thereafter and close at 2100 UTC on Tuesday, 16 September 2014.
  • The ballot page states voting closed 16 September 2014.
  • The ballot page does not state an explicit implementation or compliance effective date.
Model: gpt-5.4-mini Confidence: 0.95 Result: passed
Voting opened
2014-09-09
Voting closed
2014-09-16
Discussion opened
2014-09-02
Discussion closed
2014-09-09

AI-generated from the CABF ballot page. The official CABF article remains the authoritative source.

Excerpt

SearchHome » All CA/Browser Forum Posts » Ballot 132 – EV Code Signing Timestamp Validity Period (passed)Ballot 132 – EV Code Signing Timestamp Validity Period (passed)Voting on Ballot 132 (amending the EV Code Signing Timestamp Validity Period) closed 16 September 2014. Voting in favor were: Actalis, Comodo, DigiCert, Disig, Entrust, GlobalSign, GoDaddy, OpenTrust, Symantec, Trend Micro, WoSign, ANF, Certum, Mozilla and Microsoft. There were no votes against and no abstentions. Therefore, Ballot 132 passed.

View on cabforum.org → Last fetched 16 hours ago

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action