Rekor Public-Good Instance Hardening

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.

Post-Quantum Cryptography for Sigstore

Future-Proofing Software Supply Chain Security: Post-Quantum Cryptography for Sigstore Post-quantum cryptography (PQC) is rapidly transitioning from a theoretical exploration to an immediate infrastructure necessity. With recent advancements accelerating the estimated arrival of cryptographically relevant quantum computers (CRQCs), industry leaders like Google and Cloudflare have expedited their migration timelines to 2029, and governments have pushed up timelines to 2030 as well. To stay ahead of this threat, Sigstore is adjusting our timeline to support PQC algorithms immediately.

sigstore.dev and Rekor evolution

If you have been following the Sigstore project over the last year, you know we’ve been rolling out version 2 of Rekor, Sigstore’s transparency log. The intent was to enable signing with Rekor v2 by default, but there’s been a change of plans: the sigstore.dev public good instance will continue using Rekor v1 as the default log for the foreseeable future. Why are we staying with Rekor v1? While Rekor v2 provides greater infrastructure resiliency, it introduces breaking changes in client behavior.

Introduction sigstore-c

These days, there’s many interoperable Sigstore client libraries in various programming languages. But there are still a few places where you might struggle to run Sigstore, like on a Intel 8086 processor (first released in 1978), say running a version of DOS. Until today. Introducing sigstore-c, which focuses on portability over features (and correctness!) You can build sigstore-c on any system with a C89 compiler, including modern Linux environments with gcc or the aforementioned DOS environment with something like Open Watcom v2.

Rekor v2 GA - Cheaper to run, simpler to maintain

We are very excited to announce the General Availability of Rekor v2! Rekor v2 is a redesigned and modernized Rekor, Sigstore’s signature transparency log, transitioning its backend to a tile-backed transparency log implementation to simplify maintenance and lower operational costs. Learn more about Rekor v2 in our previous blog post announcing Alpha. We have added support for Rekor v2 upload and verification to Cosign v2.6.0, along with the Go, Python, and Java clients.