Verify Artifacts
Verify Arcane release artifacts and container images with Cosign.
Use Cosign to check that an Arcane binary or image is exactly what we published. The public key is at getarcane.app/cosign.pub and in the Arcane GitHub repository root.
Verify binaries
Section titled “Verify binaries”-
Install Cosign.
-
Download the checksum file and its Sigstore bundle from the same place as your binary (see Checksum files).
-
Verify the checksum file’s signature:
Terminal window cosign verify-blob --key "https://getarcane.app/cosign.pub" --bundle "arcane_checksums.txt.sigstore.json" "arcane_checksums.txt" -
Check the binaries you downloaded against it:
Terminal window sha256sum -c arcane_checksums.txt --ignore-missingDrop
--ignore-missingto check every file in the list.
Checksum files
Section titled “Checksum files”| Source | Checksum file | Bundle |
|---|---|---|
| GitHub Releases | arcane_<version>_checksums.txt |
arcane_<version>_checksums.txt.sigstore.json |
S3 (next binaries) |
arcane_checksums.txt |
arcane_checksums.txt.sigstore.json |
S3 (next CLI) |
arcane-cli_checksums.txt |
arcane-cli_checksums.txt.sigstore.json |
Releases v2.4.0 and earlier also have a per-file Sigstore bundle you can verify directly:
cosign verify-blob --key "https://getarcane.app/cosign.pub" --bundle "arcane-cli_linux_amd64.sigstore.json" "arcane-cli"Verify container images
Section titled “Verify container images”-
Find the image digest (the
sha256:hash of one exact image). For a local image:Terminal window docker image inspect <IMAGE_NAME_OR_ID> --format '{{index .RepoDigests 0}}'Or without pulling:
Terminal window docker buildx imagetools inspect ghcr.io/getarcaneapp/manager:latest --format "{{json .Manifest}}" | jq -r .digest -
Verify the image by digest:
Terminal window cosign verify --key "https://getarcane.app/cosign.pub" ghcr.io/getarcaneapp/manager@sha256:...