Le jeudi 5 février 2015 21:59:52 UTC+1, Kathleen Wilson a écrit : > Module #1 > Name: Mozilla CA Certificate Policy
> Module #2 > Name: CA Certificates > I propose making the following changes to the Peers list for these modules. > 2) Add Richard Barnes to the Peers list of both modules. Richard has > been contributing to Mozilla's CA program and managing Mozilla's Crypto > Engineering team for the past year, and has been working (and managing > work) on related projects including OneCRL, > https://wiki.mozilla.org/CA:RevocationPlan, > https://wiki.mozilla.org/PKI:CT, ability to add name constraints to > built-in certificates, and research into SSL cert and CA root cert usage > (more about this later, stay tuned). Many of you also know Richard from > his work in the IETF. > > 3) Add Ryan Sleevi to the Peers list of the "CA Certificates" module. > Ryan has been an active contributor to the mozilla.dev.security.policy > forum for three years. He provided technical guidance and helped refine > the updates to versions 2.1 and 2.2 of Mozilla's CA Certificate Policy, > and he regularly contributes to discussions about root inclusion/change > requests. Many of you are also aware of Ryan's active involvement in the > NSS team, Google's root program, CT, and the CA/Browser forum. Welcomed modifications. Opening module #2 to Google seems to follow some logic, as Google used (uses?) Mozilla CA list and NSS for their products, except EV program. Will that have an impact on EV+Chromium? _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
