Re: Logius PKIoverheid response to Action #2 in the January 2018 CA Communication

Thank you for the response Jochem. I am glad to hear that Logius has evaluated the risk and, given the passage of ballot 218, is moving to other methods of domain validation. - Wayne On Fri, Mar 16, 2018 at 5:55 AM, Berge, J. van den (Jochem) - Logius via dev-security-policy

Re: AC Camerfirma Chambers of Commerce and Global Chambersign 2016 Root Inclusion Request

On Thu, Mar 22, 2018 at 6:26 PM ramirommunoz--- via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > Hi Ryan > Many thanks for your report. I will try to answer to your concerns about > our root inclusión. > > > In attempt to discuss continued trust, I have attempted to

Re: AC Camerfirma Chambers of Commerce and Global Chambersign 2016 Root Inclusion Request

Hi Ryan Many thanks for your report. I will try to answer to your concerns about our root inclusión. > In attempt to discuss continued trust, I have attempted to summarize the > patterns and issues of note, along with the timeline from reporting to > remediation. It is my goal that this will

RE: DigiCert .onion certificates without Tor Service Descriptor Hash extension

True. I can tell you our process was not followed in this case, primarily because of the Symantec transaction. Ideally, when we add new products (or when a CAB Forum requirement changes), we: 1. Add the mandatory criteria to our compliance engine 2. Add the new cert to our issuing

Re: DigiCert .onion certificates without Tor Service Descriptor Hash extension

On 21 Mar 2018 17:58, Wayne Thayer via dev-security-policy wrote:7.  List of steps your CA is taking to resolve the situation and ensure such issuance will not be repeated in the future, accompanied with a timeline of when your CA expects to accomplish