On Tue, Feb 28, 2017 at 8:53 AM, douglas.beattie--- via dev-security-policy <[email protected]> wrote:
> > Yes, we're working to do just this now. While that's good and well, I do hope GlobalSign will produce an incident report regarding this matter, as to how the situation in https://groups.google.com/d/msg/mozilla.dev.security.policy/luxlU5TL2ew/qkL1ZdThAQAJ came to be in the first place. I think GoDaddy's recent explanation - https://groups.google.com/d/msg/mozilla.dev.security.policy/Htujoyq-pO8/uRBcS2TmBQAJ - may provide a model for GlobalSign here. The intent is that we don't just deal with the symptom, but that we work to understand the root cause, the scope of impact, and the opportunities for improvement. I look forward to reading GlobalSign's analysis of both this and other recent issues. _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

