I've created https://bugzilla.mozilla.org/show_bug.cgi?id=1532429 to track
this incident.
On Fri, Mar 1, 2019 at 1:55 PM David E. Ross via dev-security-policy <
dev-security-policy@lists.mozilla.org> wrote:
> On 2/28/2019 7:45 PM, 孙圣男 wrote:
> > Dear Mozilla：
> > This problem had been confi
On 2/28/2019 7:45 PM, 孙圣男 wrote:
> Dear Mozilla：
> This problem had been confirmed. We contacted the customer and
> confirmed this certificate haven't been deployed to production system, no
> damage is caused. This certificate had been revoked in March 1, 2019. We had
> fixed this bug in Febr
Hi Jonathan,
When something like this occurs the Mozilla community asks for an incident
report explaining how the incident occurred, what was done to remediate it,
and what procedures and technical controls have been put in place to
prevent a future recurrence of the problem. You can see documenta
Dear Mozilla：
This problem had been confirmed. We contacted the customer and
confirmed this certificate haven't been deployed to production system, no
damage is caused. This certificate had been revoked in March 1, 2019. We had
fixed this bug in February 27 update.
Best wishes!
Jonathan Sun
4 matches
Mail list logo
