Is there an expectation of a resolution of some sort to this matter? Also, their most recent audit is apparently overdue (perhaps related to the SHA-1 mis-issuance?)
https://groups.google.com/d/msg/mozilla.dev.security.policy/IjgFwzGI_H0/-689uFoXBwAJ On Thursday, March 16, 2017 at 7:00:51 AM UTC-4, Gervase Markham wrote: > Hi Blake, > > On 02/03/17 16:26, [email protected] wrote: > > We have engaged with our external auditors in relation to this and the > > previous certificate that was reported. Once that activity has concluded we > > will be providing further information. > > Do you have an ETA for this incident report? It's been quite some time > now. I am still interested to understand how a "full investigation" of > the first certificate failed to turn up the second. > > Gerv _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

