On Friday, February 8, 2019 at 7:25:08 PM UTC-8, Jakob Bohm wrote:
> On 09/02/2019 01:36, Santhan Raj wrote:
> > On Friday, February 8, 2019 at 4:09:32 PM UTC-8, Joanna Fox wrote:
> >> I agree on the surface this bug appears to be the same, but the root cause
> >> is a different. The issue for bug
On 09/02/2019 01:36, Santhan Raj wrote:
On Friday, February 8, 2019 at 4:09:32 PM UTC-8, Joanna Fox wrote:
I agree on the surface this bug appears to be the same, but the root cause is a
different. The issue for bug 1462844 was a specific status not counting as
active when it was. To mitigate
On Friday, February 8, 2019 at 4:09:32 PM UTC-8, Joanna Fox wrote:
> I agree on the surface this bug appears to be the same, but the root cause is
> a different. The issue for bug 1462844 was a specific status not counting as
> active when it was. To mitigate this issue, we updated the query to i
I agree on the surface this bug appears to be the same, but the root cause is a
different. The issue for bug 1462844 was a specific status not counting as
active when it was. To mitigate this issue, we updated the query to include the
missing status. However, we are in the process of simplifying
Good catch, thanks Wayne!
I also realized it sounds very similar to
https://bugzilla.mozilla.org/show_bug.cgi?id=1526154 from DigiCert, which
similarly included an overly-restrictive query.
It's also similar to Symantec's incident investigation in
https://wiki.mozilla.org/CA:Symantec_Issues#Issue
Perhaps more concerning, this sounds a lot like bug #1462844 in which
misissued certificates were reported that had not been found and revoked
despite GoDaddy having previously scanned their database for the issue.
GoDaddy never identified or described how they would remediate the cause of
that bug
Thanks Joanna,
Just to make sure - this is
https://bugzilla.mozilla.org/show_bug.cgi?id=1524815 correct?
If so, this sounds remarkably similar to the root cause analysis that
Entrust shared, in https://bugzilla.mozilla.org/show_bug.cgi?id=1521520 .
Similar to that issue, please provide an update
GoDaddy received a certificate problem report on 1/29/2019 for 2 unrevoked
unexpired certificates have underscores in the DNS name that did not meet the
January 15th deadline for revocation. The certificates reported are as follows:
https://crt.sh/?opt=zlint&id=626981823
https://crt.sh/?opt=zlint
8 matches
Mail list logo