FIRMAPROFESIONAL: Delayed leaf revocation
This case reports a delayed leaf revocation by FIRMAPROFESIONAL. The CA stated that, as referenced in bug #1889420, its procedure revoked all affected certificates in less than 5 days except for one certificate. On April 9, it was communicated that revocation of the remaining certificate was not possible because it was located in essential and critical hospital and healthcare systems of a public administration, and the certificate holder requested additional time to replace it. The CA reported staying in continuous contact with the client and, after confirming the certificate change, completing the revocation at 10:21 AM (UTC) on April 12. The CA stated there was no impact in terms of security, usability, compatibility, or business for its clients or the community, and that only one certificate was affected by the delay. Mozilla asked whether this was a delayed incident report or a delayed leaf revocation, and the CA confirmed it was a delayed leaf revocation. The bug is resolved with resolution FIXED.
- A referenced revocation investigation identified affected certificates and planned revocation within 5 days.
- Revocation of one remaining certificate was reported as not possible due to critical hospital/healthcare system usage.
- The delayed leaf certificate was revoked at 10:21 AM (UTC) after the client confirmed replacement.
- Logalty representative — Reported that all but one affected certificate were revoked within 5 days, explained why the last revocation was delayed, and stated the final revocation occurred at 10:21 AM (UTC) on April 12.
- Mozilla representative — Asked whether the report was a delayed incident report or a delayed leaf revocation.
- Logalty representative — Confirmed it was a delayed leaf revocation.
- Mozilla representative — Suggested closing the bug sometime next week (May 27–31) if there were no further comments.