EV Code Signing

Voting on Ballot 172, “Removal of Permanent Identifier” has now closed. The results are as follows: From the CAs, we received 9 YES votes, 1 NO vote and 7 Abstentions From the Browsers, we received 1 YES vote, 0 NO votes and 0 Abstentions Therefore the ballot passes.  Full results can be seen on the ballot tracker: https://docs.google.com/spreadsheets/d/1FBsMZjlzyvK3mFR1u4qMqvZwlI86yJ-v0am1pCBo8uI/edit#gid=4 Dean Coclin …

Pursuant to Section 4.1 of the CA/Browser Forum’s IPR Policy, this is notice of the commencement of a 30-day IPR maintenance-guideline review period by which certain provisions of the IPR will become applicable to these recent changes made to the EV Code Signing Guidelines by Ballot 117. Ballot 117 clarified what is allowed in the Common Name and Subject Alternative …

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. Nay: Comodo, Network Solutions, and Google. Abstain: Buypass Results: Ballot passed Updated version is posted here on the EV Code Signing page. Jeremy Rowley of DigiCert made the following motion, …

Ballot 70 – EV Code Signing Identifier (Passed Unanimously) Motion Jeremy Rowley made the following motion, and Tom Albertson and Bruce Morton endorsed it: … Motion begins…. Effective immediately. … Erratum begins … DELETE the following text from the EV Guidelines Appendix H: “(3) Certificate Content. EV Code Signing Certificates MUST meet the minimum content requirements of Section 8.1 and …