Sorry for the delayed reply here, but in the process of being surprised that there are still CAs with delays > 90 days, I was looking through historic patterns, and noticed this CA is a repeat from the year prior.
That is, this CA, https://www.mail-archive.com/dev-security-policy@lists.mozilla.org/msg13051.html , had the same issue last year as well, https://www.mail-archive.com/dev-security-policy@lists.mozilla.org/msg12100.html Should we be creating CA incidents for repeats? I wasn’t sure if this was just an administrative hiccup on the Mozilla side in processing the case, or if this is a matter where the CA is not disclosing in a timely fashion. On Tue, Mar 3, 2020 at 12:30 PM Kathleen Wilson via dev-security-policy < dev-security-policy@lists.mozilla.org> wrote: > -------- Forwarded Message -------- > Subject: Summary of March 2020 Outdated Audit Statements for > Intermediate Certs > Date: Tue, 3 Mar 2020 15:00:16 +0000 (GMT) > > CA Owner: AC Camerfirma, S.A. > - Certificate Name: InfoCert Organization Validation CA 3 > SHA-256 Fingerprint: > 247A6D807FF164031E0EB22CA85DE329A3A4E6603DBC6203F0C6E282A9C9EA84 > Standard Audit Period End Date (mm/dd/yyyy): 12/02/2018 > BR Audit Period End Date (mm/dd/yyyy): 12/02/2018 > > > > _______________________________________________ > dev-security-policy mailing list > dev-security-policy@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-security-policy > _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
