What about code signing and s/MIME certs? Code signing is still used by MS for legacy software until Jan 2017.
-----Original Message----- From: dev-security-policy [mailto:dev-security-policy-bounces+jeremy.rowley=digicert.com@lists.mozilla .org] On Behalf Of [email protected] Sent: Tuesday, March 22, 2016 10:49 AM To: [email protected] Subject: Re: Drafting Q1 2016 CA Communication On Tuesday, March 22, 2016 at 9:33:19 AM UTC-7, [email protected] wrote: > The following 'ACTION #1c' has been added to the communication, which is here: > https://wiki.mozilla.org/CA:Communications#March_2016 > and click on "Link to DRAFT of March 2016 CA Communication". > Also, I have filled in proposed dates, assuming I send the communication next week. I used two dates... April 22,2016 -- the date by which CAs must enter their initial response to this communication into the CA Community in Salesforce. June 30, 2016 -- the date by which CAs must take the requested actions: enter intermediate cert data into the CA Community in Salesforce, and stop issuing certs with the problems listed in ACTION #4. I would especially like to hear from CAs in regards to if these dates are reasonable. Thanks, 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
