← Entrust cases
Bugzilla #1879602 Security Incident Self Reported Incident

Entrust: OCSP response signed with SHA-1

RESOLVED FIXED Entrust
This summary was auto-generated by AI and revised by me when needed — accuracy improves with each update. Always refer to the official Bugzilla thread as the authoritative source. If you spot an inaccuracy, let me know via the contact form.
AI Summary

Entrust identified that two of its root CA OCSP responders were signing responses using the SHA-1 algorithm, which is non-compliant with the CA/Browser Forum's requirements. This issue was discovered on February 3, 2024, through monitoring by OCSP Watch. Entrust promptly scheduled a fix, which was implemented on February 6, 2024, to ensure that OCSP responses would be signed with SHA-256 instead. The root cause was attributed to a failure to update the online OCSP responders in line with the SHA-1 sunset date. Entrust has since updated its operational procedures to prevent similar issues in the future. The incident has been resolved and all action items completed.

Model: gpt-4o-mini Generated: 2026-06-13 21:35 UTC Revised: 2026-06-16 18:54 UTC Confidence: 0.85 30 comments
Chronology
  1. Operations reviewed OCSP Watch and discovered SHA-1 signing issue.
  2. Fix applied to production to switch OCSP signing to SHA-256.
Thread Activity
  1. Entrust representative — Summary of the incident and actions taken was provided.
  2. Entrust representative — Monitoring using OCSP Watch was added and action items completed.
  3. Entrust representative — All actions are complete. Requesting to close this incident.
Participants
Entrust representative Internet Security Research Group Community commenter Apple representative Mozilla representative
Similar Local Cases
#1894111 RESOLVED Ca Documents Self Reported Incident Opened 2024-04-29 · Closed 2025-01-22 · 100% similar
Entrust: Not updating CPR Problem Reporting Mechanism fields in CCADB
#1897630 RESOLVED Self Reported Incident Opened 2024-05-19 · Closed 2024-08-15 · 100% similar
Entrust: Jurisdiction issue in some EV TLS & Code Signing certificates
#1867130 RESOLVED Self Reported Incident Opened 2023-11-28 · Closed 2024-05-10 · 100% similar
Entrust: Jurisdiction Locality Wrong in EV Certificate
#1921387 RESOLVED Self Reported Incident Opened 2024-09-27 · Closed 2025-03-18 · 96% similar
Entrust: Improperly Verified Business Category
#1914999 RESOLVED Self Reported Incident Opened 2024-08-26 · Closed 2025-02-28 · 88% similar
Entrust: S/MIME OrgID Country not matching C field
#1952635 RESOLVED Self Reported Incident Opened 2025-03-08 · Closed 2025-08-11 · 88% similar
Entrust: Missing or Inconsistent Disclosure of S/MIME BR Audits
#1448986 RESOLVED Self Reported Incident Opened 2018-03-26 · Closed 2023-02-22 · 88% similar
Entrust: IP Address in dNSName form
#1658792 RESOLVED Self Reported Incident Opened 2020-08-12 · Closed 2023-02-22 · 86% similar
Entrust: Invalid data in State/Province Field

We use only essential cookies and local browser storage for preferences and security. See our Privacy Policy for details.

Confirm action