Verifying Rekor Releases
Before running a downloaded Rekor binary or deploying a Rekor container image, you should verify its authenticity.
Starting with Rekor v1.6.0, release binaries and container images are signed in two ways:
- GitHub Artifact Attestations: SLSA build provenance attestations signed using GitHub Actions’ OIDC identity, verifiable with the GitHub CLI (
gh). - Sigstore’s release artifact signing key (
artifact.pub): Cryptographic signatures generated with Google Cloud KMS and recorded in the Rekor transparency log, verifiable with Cosign.
In the commands below, replace <version> (for example, v1.6.0), <binary> (rekor-cli or rekor-server), <os> (linux or darwin), and <arch> (amd64 or arm64) with the release version, binary, and platform you are verifying.
Verifying with GitHub Artifact Attestations (gh CLI)
Verify the Rekor binary
Download the binary from the Rekor releases page and verify its attestation with gh attestation verify:
curl -sSfLO "https://github.com/sigstore/rekor/releases/download/<version>/<binary>-<os>-<arch>"
gh attestation verify "<binary>-<os>-<arch>" \
--repo sigstore/rekor \
--signer-workflow sigstore/rekor/.github/workflows/release.yml
Verify the Rekor container image
Release container images are published to ghcr.io/sigstore/rekor/rekor-server and ghcr.io/sigstore/rekor/rekor-cli with their attestations attached as OCI referrers:
gh attestation verify "oci://ghcr.io/sigstore/rekor/<binary>:<version>" \
--repo sigstore/rekor \
--signer-workflow sigstore/rekor/.github/workflows/build_container.yml \
--bundle-from-oci
Verifying with the Artifact Signing Key (cosign)
Retrieve the artifact signing key (artifact.pub)
You can retrieve artifact.pub securely using The Update Framework (TUF) client:
go install github.com/theupdateframework/go-tuf/v2/examples/cli/tuf-client@latest
curl -sSfLo root.json https://raw.githubusercontent.com/sigstore/root-signing/refs/heads/main/metadata/root_history/10.root.json
tuf-client init --url https://tuf-repo-cdn.sigstore.dev -f root.json
tuf-client get --url https://tuf-repo-cdn.sigstore.dev -t https://tuf-repo-cdn.sigstore.dev/targets artifact.pub
cp tuf_download/artifact.pub ./artifact.pub
Alternatively, you can download artifact.pub from the sigstore/root-signing repository:
curl -sSfLO https://raw.githubusercontent.com/sigstore/root-signing/main/targets/artifact.pub
Verify the Rekor binary
For Rekor v1.4.3 and later
Download the binary and its corresponding .sigstore.json bundle from the release, then verify with cosign verify-blob:
curl -sSfLO "https://github.com/sigstore/rekor/releases/download/<version>/<binary>-<os>-<arch>"
curl -sSfLO "https://github.com/sigstore/rekor/releases/download/<version>/<binary>-<os>-<arch>.sigstore.json"
cosign verify-blob \
--key artifact.pub \
--bundle "<binary>-<os>-<arch>.sigstore.json" \
"<binary>-<os>-<arch>"
For Rekor v1.4.2 and earlier
Releases prior to v1.4.3 published detached base64-encoded .sig signatures instead of .sigstore.json bundles:
curl -sSfLO "https://github.com/sigstore/rekor/releases/download/<version>/<binary>-<os>-<arch>"
curl -sSfLO "https://github.com/sigstore/rekor/releases/download/<version>/<binary>-<os>-<arch>.sig"
base64 -d < "<binary>-<os>-<arch>.sig" > "<binary>-<os>-<arch>.sig.decoded"
openssl dgst -sha256 -verify artifact.pub -signature "<binary>-<os>-<arch>.sig.decoded" "<binary>-<os>-<arch>"
Verify the Rekor container image
Use cosign verify with artifact.pub to verify the signed container image on GHCR:
cosign verify \
--key artifact.pub \
-a "GIT_VERSION=<version>" \
"ghcr.io/sigstore/rekor/<binary>:<version>"
Note: Rekor v1.6.0+ container signatures use the Sigstore bundle format (cosign v3 default). If you are verifying with cosign v2.x, pass --new-bundle-format (note that -a annotation checks are not supported with --new-bundle-format in cosign v2.x).