Hi Kathleen, As discussed below, the changes were submitted and approved and we now have new versions of the CP and CPS, however rather than send around this list I prefer them to be published following our standard internal operating procedures (which will take a few more days). However in saying this I've updated to the bug the salient text changes for 3.2.2 and a new section 3.2.7. We now indicate what we do for ALL SSL certificates including EV.
I hope the discussion can continue in the meantime for approval of our ECC roots. Thanks to all for their feedback which helped improve our public documents. Steve > -----Original Message----- > From: Steve Roylance [mailto:[email protected]] > Sent: 22 August 2014 06:45 > To: Kathleen Wilson > Cc: [email protected] > Subject: Re: GlobalSign Request to Include ECC Roots > > Hi Kathleen. > > I'm on vacation next week. > > The changes that make clarifications to our processes, particularly around > domain verification and EV, have been submitted for approval. I hope to have > a > new version ready by the week of Sept 1st. > > Steve > > Sent from my iPhone > > > On 21 Aug 2014, at 23:25, Kathleen Wilson <[email protected]> wrote: > > > >> On 7/29/14, 3:26 PM, Kathleen Wilson wrote: > >> GlobalSign has applied to include the “GlobalSign ECC Root CA - R4” and > >> “GlobalSign ECC Root CA - R5” root certificates, and turn on all three > >> trust bits and enable EV treatment for both roots. > > > > > > Thanks to those of you who have already contributed to this discussion. > > > > While we wait for GlobalSign to update their CPS... > > > > Does anyone else have comments/questions/concerns about this request? > > > > Kathleen > > > > _______________________________________________ > > dev-security-policy mailing list > > [email protected] > > https://lists.mozilla.org/listinfo/dev-security-policy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
