← Entrust cases
Bugzilla #1512018 Ca Certificate Compliance Self Reported Incident

Entrust: Certificate issued with '-' in ST field

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 discovered a compliance issue where an SSL certificate was issued with a '-' character in the ST field of the subject DN, violating CA/B Forum Baseline Requirements. The issue was identified on November 20, 2018, just one day after the certificate was issued on November 19, 2018. Entrust initiated an investigation and updated their processes to prevent future occurrences. The problematic certificate was revoked on November 26, 2018. Remediation steps included alerting the verification team and implementing software changes to block invalid ST attributes. The issue has since been addressed with pre-issuance linting as of May 14, 2019.

Model: gpt-4o-mini Generated: 2026-06-13 17:57 UTC Revised: 2026-06-16 18:37 UTC Confidence: 0.85 12 comments
Chronology
  1. Certificate issued with '-' in ST field
  2. Miss-issuance detected and investigation started
  3. Miss-issued certificate revoked
  4. Remediation completed with pre-issuance linting
Thread Activity
  1. Entrust representative — Reported the certificate issuance issue and the steps taken.
  2. Community commenter — Requested a detailed timeline and expressed concerns about the verification process.
  3. Community commenter — Inquired about updates on the incident report.
  4. Fastly representative — Confirmed that remediation has been completed.
Participants
Community commenter
External References
Related Bugzilla IDs Mentioned
Similar Local Cases
#1627346 RESOLVED Ca Certificate Compliance Self Reported Incident Certificate Misissuance Delayed Revocation Opened 2020-04-03 · Closed 2023-02-22 · 100% similar
Entrust: S/MIME Certificate Issued with Incorrect Policy OID
#1561013 RESOLVED Self Reported Incident Certificate Misissuance Opened 2019-06-24 · Closed 2023-02-22 · 99% similar
Entrust: Certificate issued with validity greater than 825-days
#1648472 RESOLVED Self Reported Incident Opened 2020-06-25 · Closed 2024-06-30 · 99% similar
Entrust: SHA-256 hash algorithm used with ECC P-384 key
#1673119 RESOLVED Self Reported Incident Opened 2020-10-23 · Closed 2023-02-22 · 99% similar
Entrust: Subscriber provides private key with CSR
#1552562 RESOLVED Ca Certificate Compliance Opened 2019-05-17 · Closed 2023-02-22 · 98% similar
Entrust: Question marks in certificate O and L fields
#1635096 RESOLVED Self Reported Incident Opened 2020-05-04 · Closed 2023-02-22 · 93% similar
Entrust: Printable String Constraint Failure
#1914999 RESOLVED Self Reported Incident Opened 2024-08-26 · Closed 2025-02-28 · 89% similar
Entrust: S/MIME OrgID Country not matching C field
#1696227 RESOLVED Ca Certificate Compliance Certificate Misissuance Revocation Issue Opened 2021-03-03 · Closed 2023-02-22 · 89% similar
Entrust: Incorrect Jurisdiction Country Value in an EV Certificate

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

Confirm action