Re: .tg Certificates Issued by Let's Encrypt

2017-11-13 Thread Jakob Bohm via dev-security-policy
On 14/11/2017 02:23, Kathleen Wilson wrote: On 11/6/17 3:40 AM, Ben Laurie wrote: Since CT is not (yet) compulsory, it seems you probably have to contact all CAs, doesn't it? To close the loop on this... I have added the following to the draft of the November 2017 CA Communication. ~~

Re: .tg Certificates Issued by Let's Encrypt

2017-11-13 Thread Kathleen Wilson via dev-security-policy
On 11/6/17 3:40 AM, Ben Laurie wrote: Since CT is not (yet) compulsory, it seems you probably have to contact all CAs, doesn't it? To close the loop on this... I have added the following to the draft of the November 2017 CA Communication. ~~ ACTION 8: Check for issuance of TLS/SSL

Re: DRAFT November 2017 CA Communication

2017-11-13 Thread Kathleen Wilson via dev-security-policy
All, I have updated the draft of the November 2017 CA Communication as follows: - Postponed the response deadline to December 15. - Removed the CT item (that will be handled separately, later) - Added an action item (#4) about full period-of-time audits with no gaps. (resulted in a slight

Re: New Sub CAs under the DigiCert RSA and ECC Transition Roots

2017-11-13 Thread Kathleen Wilson via dev-security-policy
On 11/10/17 1:44 PM, Ben Wilson wrote: In the spirit of full transparency and in attempt to comply to the extent we can with Mozilla policy, on Thursday, Nov. 2, we created several sub CAs under two new "transition" roots (yet to be submitted as roots). These sub CAs haven't been uploaded yet