CA/Browser Forum
Home » All CA/Browser Forum Posts

CA/Browser Forum posts

Filter posts by Author, Tag or Series

Forum Releases Final Code Signing Baseline Requirements for Vote
August 11, 2015 by Ben WilsonThe Code Signing Working Group of the CA/Browser Forum announces the ballot of the final draft of the Code Signing Baseline Requirements. This version takes into account comments received in the first and second rounds of public review, comments from WebTrust auditors, and an additional three months of editing by the Working Group. Code Signing Requirements 2015-11-19 This is ballot 158 which begins on December 3, 2015 Dean Coclin CA/B Forum Chair
2015-08-06 Minutes
August 6, 2015 by Ben WilsonFinal Minutes August 6, 2015 Attendees: An Ying (CNNIC), Atsushi Inaba, Ben Wilson, Billy VanCannon, Christy McKinley, Dean Coclin, Charlotte Yan (CNNIC), Doug Beattie, Eddy Nigg, Gerv Markham, Jeremy Rowley, , Kirk Hall, Mads Henriksveen, Marcelo Silva, Patrick Tonnier, Peter Miscovic, Rick Andrews, Robin Alden, Ryan Sleevi, Sisel Hoel, Tim Shirley, Tim Hollebeek, Volkan Nergiz, Wayne Thayer
2015-07-23 Minutes
July 23, 2015 by Ben WilsonMinutes July 23, 2015 Attendees: Atsushi Inaba, Ben Wilson, Billy VanCannon, Bruce Morton, Dean Coclin, Dimitris Zacharopoulos, Gerv Markham, Jeremy Rowley, Jody Cloutier, Kirk Hall, Mads Henriksveen, Mat Caughron, Patrick Tonnier, Peter Miscovic, Rick Andrews, Stephen Davidson, Tim Hollebeek, Wayne Thayer
Ballot 149 – Membership Criteria Clarification
July 10, 2015 by Ben WilsonVoting on Ballot 149 (Membership criteria clarification) has closed. The Forum received 17 YES votes from CA members: Buypass, Chungwa Telecom, Disig, Entrust, Globalsign, GoDaddy, HARICA, Logius PKIoverheid, OpenTrust, QuoVadis, SSC, Symantec, Trend Micro, Trustwave, TurkTrust, Visa and WoSign and 3 YES votes from Browser members: Google, Opera and Mozilla. Three Abstain votes were received from CA members Actalis, ANF, OATI. There were 0 NO votes. Therefore the ballot passes.
2015-07-09 Minutes
July 9, 2015 by Ben WilsonApproved Minutes July 9, 2015 Attendees: Atsushi Inaba, Ben Wilson, Billy VanCannon, Bruce Morton, Burak Kalkan, Davut Tokgoz, Dean Coclin, Doug Beattie, Gerv Markham, Jody Cloutier, Kirk Hall, Mads Henriksveen, Mat Caughron, Patrick Tonnier, Peter Miscovic, Rick Andrews, Robin Alden, Tim Hollebeek, Tim Shirley, Volkan Nergiz, Wayne Thayer, Marcelo Silva, Dimitris Zacharopoulos
Ballot 147 – Attorney Accountant Letter Changes
June 25, 2015 by Ben WilsonBallot 147 – Attorney-Accountant Letter Changes Voting on Ballot 147 has closed. Here are the results:
Minutes of the F2F 35 Meeting in Zurich, Switzerland, 23-25 June 2015
June 24, 2015 by Ben WilsonMeeting 35 Minutes Day 1 Wednesday, 24 June 2015
2015-06-11 Minutes
June 11, 2015 by Ben WilsonMinutes of Teleconference – 11 June 2015 Read Antitrust Statement. The Statement was read.
2015-05-28 Minutes
May 28, 2015 by Ben WilsonCA/Browser Forum Minutes of May 28, 2015 Attendees: Atsushi Inaba, Atilla Biler, Ben Wilson, Billy VanCannon, Bruce Morton, Connie Enke, Dean Coclin, Doug Beattie, Gerv Markham, Jeremy Rowley, Jody Cloutier, Kubra Zaray, Mads Henriksveen, Mat Caughron, Patrick Tronnier, Peter Miscovic, Rick Andrews, Robin Alden, Ryan Sleevi, Sissel Hoel, Tim Hollebeek, Tim Shirley, Volkan Nergiz, Wayne Thayer Minutes of 14 May meeting were approved. These will be posted to the public list.
2015-05-14 Minutes
May 14, 2015 by Ben WilsonMinutes May 14, 2015 Attendees: Dean Coclin, Ben Wilson, Doug Beattie, Gerv Markham, Atsushi Inaba, Kirk Hall, Atilla Biler, Bruce Morton, Burak Kalkan, Cecilia Kam, Davut Tokgoz, Volkan Nergiz, Rick Andrews, Moudrick Dadashov, Eddy Nigg, Mat Caughron, Tim Hollebeek, Patrick Tronnier, Billy VanCannon, Jeremy Rowley, Robin Alden, Ryan Sleevi Minutes of 30 April meeting were approved. These will be posted to the public list. Ballots: Ballot 149 (Bylaw updates from Kirk): Kirk wants to hold the ballot until the WebTrust audit team determines what the new name of the audit will be. Domain Validation Ballot*: There are a few open issues on this ballot:Working on revising #10 from the list. Some folks were concerned with the “test cert” provision. Tim H said the test cert should be allowed and that #10 needs to be tightened up. A longer discussion in the working group is warranted. Kirk also said it needs more details to make it more like methods 6-9 (which are explicit). Ryan also agreed. Jeremy said he put Doug’s proposed method in the proposal for now. The “random value” was 128 bits but Kirk wanted it back to 112 bits. Kirk said that 128 bits was overkill. The random value is provided by the CA to applicants so it’s not practically predictable by hackers. Kirk felt the lower value is adequate (and is commonly used for some other purpose). Ryan disagreed and said there were threats like reversible random number generators and things like passive observation which may allow for reconstruction of the RNG. He would like to see the standard to be 128 bits. Tim said he also had these concerns but after looking into Java Secure random generator (which apparently doesn’t do 128 bits) he felt it was cryptographically secure and is no longer concerned. Gerv said the cryptographic strength of the generator is more important than the bit size but feared that specifying a smaller key size would lead people to use a less secure RNG. Kirk challenged the security issue. Ryan further explained (and said we should err on the side of caution) that a network based adversary could observe traffic sent to a CA’s customer and (theoretically) predict a random number challenge sent to a future customer and cause a miss-issuance which is not the CA’s fault. Gerv suggested a compromise of specifying a cryptographically strong random number generator (with a lower key size) instead of specifying a higher key size (which would include the Java generator but not the Windows GUID generator). Doug said an adversary could submit an order and get a random string back w/o monitoring the network (Ryan’s example threat). Ryan said it depends on the type of cert (OV/EV vs DV). Rick said how would an auditor determine if a RNG is cryptographically secure. Ryan said in theory they should but in reality, recent reports and events prove they probably don’t. But he said it could be an auditable requirement. Tim H. said that in the financial industry, this type of thing gets audited all the time. Kirk said this is not the place we should be focusing this type of effort. Ryan asked what harm a requirement for 128 bits would cause. Kirk said what CAs are using today may not meet that requirement and it would be a wasted effort to get people to switch for no real benefit. Ryan said there are already requirements for cryptographically strong random number generators but Kirk said for this issue, it wasn’t that important. Discussion was terminated due to time constraints.
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).