Open Bug 2092771 Opened 3 days ago Updated 1 hour ago

IdenTrust: Issuance of Timestamping Certificate with CP/CPS discrepancies

Categories

(CA Program :: CA Certificate Compliance, task)

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: roots, Assigned: roots)

Details

(Whiteboard: [ca-compliance] [policy-failure])

Preliminary Incident Report

Summary

  • Incident description:
    During the comprehensive certificate profile review initiated in response to Bug 2085436, we identified an inconsistency between the TrustID Non-TLS CP/CPS v5.1.1 and the Code Signing Baseline Requirements regarding the criticality of the extendedKeyUsage extension in timestamping certificates. The TrustID Non-TLS CP/CPS specifies that the extension must be non-critical, whereas the Code Signing Baseline Requirements require it to be critical.

    Our investigation identified two active timestamping certificates with the extension correctly marked critical and no non-active certificates. Both identified certificates conform to the applicable Code Signing Baseline Requirements for this extension but do not conform to the published TrustID Non-TLS CP/CPS. We traced the discrepancy to the consolidation of the CP/CPS as well as separation into purpose-specific markdown documents During this process, the timestamping certificate profile in TrustID Non-TLS CP/CPS v5.0.0, effective October 30, 2025, incorrectly specified the extension as non-critical.

    We will update the TrustID Non-TLS CP/CPS within to correctly specify that the extendedKeyUsage extension must be marked critical bring policy into alignment with the Code Signing Baseline Requirements and our existing certificate issuance practices. As revoking these timestamping certificates may have impact on the Microsoft code signing ecosystem we will reach out to Microsoft to make them aware of the impending revocation.

  • Relevant policies:

  • Source of incident disclosure: Self Reported

Assignee: nobody → roots
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Whiteboard: [ca-compliance] [policy-failure]
You need to log in before you can comment on or make changes to this bug.