Hardening Sigstore Public Infrastructure
To harden our public-good infrastructure and reduce attack surfaces, we are reducing the number of supported entry types on the Sigstore public deployment transparency log.
Effective immediately, we will disable the upload of a number of Rekor entry types, all of which are unsupported by Sigstore client tooling and have single-digit uploads in a 90-day window.
This change will have no impact for users of Cosign and Sigstore SDKs, as well as integrators using these client libraries.
Hardening the infrastructure and minimizing API surface reduces the risk of parsing vulnerabilities and denial-of-serivce attacks.
Supported Entry Types Moving Forward
The Sigstore public deployment will exclusively support the following entry types:
hashedrekord: The standard format representing a hashed artifact and its signature.dsse: Used for in-toto attestation signing.intoto(versions v0.0.1 and v0.0.2): A previous revision of thedssetype, still supported by older clients.rekord: Used in older versions of Cosign and Rekor’s CLI that sends the full payload to Rekor.hashedrekordshould always be used instead.helm: Supporting Helm chart provenance. Please reach out if you’re relying on this plugin or open to contributing changes to make it conformant with other clients.
SDK Recommendation for Developers
If you are developing or maintaining a Sigstore client or integration, your implementation should exclusively generate hashedrekord entries.
This type represents the well-supported path for the vast majority of signing use cases, including container signing, blob signing, and general attestation envelopes.
Optionally, when integrating with Rekor v1, your implementation may generate dsse entries for server-side payload generation, although large attestations are unsupported.
For newer integrations, we recommend leveraging Rekor v2, which is well-optimized for all client payloads, including large attestations.
What Does This Mean for You?
- For Most Users: If you use official Sigstore tools (like Cosign) or official language SDKs (Go, Python, JS, Rust, Ruby), no action is required. These tools already default to the supported types.
- For Private Deployments: These additional types continue to be supported in the Rekor codebase, so you may continue to use them, though we recommend migrating to use
hashedrekord. - For Custom Integrations: If you have built custom client integrations that rely on unsupported Rekor entry types, you will need to migrate your client payload generation to use
hashedrekordordsse.
If you have any questions, feel free to reach out on the Sigstore Slack or open an issue on the Rekor GitHub repository.
