Skip to content
Get ProGet Pro

Verify a release

Verify Guard's checksums, Sigstore signatures, SLSA provenance and Linux reproducibility.

Guard holds a key that can trade your account. The release provides several checks connecting the downloaded files to the public source and build.

Use this page to check a release before running it. Return to the setup journey for installation and paper-mode verification.

Download all release assets with the GitHub CLI, then verify SHA256SUMS with cosign:

Terminal window
gh release download v1.0.2 --repo zunderlabs/zunder-guard --dir guard-v1.0.2
cd guard-v1.0.2
cosign verify-blob --bundle SHA256SUMS.sigstore.json \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/zunderlabs/zunder-guard/.github/workflows/release.yml@refs/tags/v1.0.2 \
SHA256SUMS
sha256sum -c SHA256SUMS
# macOS without sha256sum: shasum -a 256 -c SHA256SUMS

The signature binds the checksums to this repository’s release workflow at this exact tag. Checksums alone catch a damaged download, but do not prove who made it. When downloading just one archive, compare that file’s SHA-256 with its line in the verified SHA256SUMS.

Windows uses the same cosign verify-blob command. Compare the Windows zip with its signed checksum:

Terminal window
Get-FileHash zunder-guard-v1.0.2-windows-amd64.zip -Algorithm SHA256

Use slsa-verifier to check the provenance against the source repository and tag:

Terminal window
slsa-verifier verify-artifact zunder-guard-v1.0.2-linux-arm64.tar.gz \
--provenance-path zunder-guard-v1.0.2.intoto.jsonl \
--source-uri github.com/zunderlabs/zunder-guard \
--source-tag v1.0.2

The generic SLSA generator records the source and workflow context for the checksummed artifacts. It does not by itself prove that a binary implements the source correctly.

The signed checksums include zunder-guard-v1.0.2.image.txt, which names the immutable image digest. Use that reference rather than resolving a moving tag:

Terminal window
REF=$(cat zunder-guard-v1.0.2.image.txt)
cosign verify "$REF" \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-identity https://github.com/zunderlabs/zunder-guard/.github/workflows/release.yml@refs/tags/v1.0.2
slsa-verifier verify-image "$REF" \
--source-uri github.com/zunderlabs/zunder-guard --source-tag v1.0.2

The image contains the same Linux binaries as the signed archives and has a signed SPDX SBOM attestation.

Linux builds run twice on fresh native runners and must match byte for byte. To repeat that comparison, use Docker Buildx from the public source at the release tag and compare the binary with the verified archive:

Terminal window
git clone https://github.com/zunderlabs/zunder-guard source
cd source
git checkout v1.0.2
docker buildx build -f deploy/guard/Dockerfile --target bin-build \
--platform linux/arm64 --no-cache -o type=local,dest=rebuilt .
mkdir archive
tar -xzf ../zunder-guard-v1.0.2-linux-arm64.tar.gz -C archive
cmp rebuilt/zunder-guard archive/zunder-guard

Use linux/amd64 and the linux-amd64 archive on an x86 machine. macOS and Windows are built with pinned toolchains and normalized paths; Guard 1.0 does not claim a verified byte-for-byte rebuild for those platforms. Report a Linux mismatch through Reporting a vulnerability.

Five binary archives: Linux and macOS for x86-64 and ARM64 (.tar.gz), Windows x86-64 (.zip). Each contains ELv2, the copyright notice and third-party licence texts. Other assets include i, i.ps1, install.sh, the Homebrew formula, optional winget manifests, pinned deployment templates, SPDX and CycloneDX dependency SBOMs, the signed checksums, the image digest reference and SLSA provenance. CI runs cargo deny check for dependency licences and advisories.

The AWS quick-create link uses a versioned S3 copy of cloudformation.yaml. Its bytes must match the release asset covered by the signed SHA256SUMS.

This page as plain Markdown, for people and LLMs: /docs/deploy/verify.md