Skip to the content

Verify a download

How to check an AgentGarm download's SHA-256 and its minisign signature before you run it.

Why both checks

The SHA-256 proves the file is the one listed in SHA256SUMS. The minisign signature proves SHA256SUMS was signed with the release key, which never leaves the release machine. So a file altered where the downloads are stored fails the check.

Both checks rest on the key you check against. If you take it from this site, they cannot catch this site itself being changed: compare it with a copy from somewhere else, such as one we send you from support@nannertech.com. A valid signature also does not say a release is the newest or has not been withdrawn: the download page says that.

1. Download the checksums and their signature

From the same release as your file: SHA256SUMS and SHA256SUMS.minisig, and the release key. The release key is published with the first release.

curl -fLO https://agentgarm.com/download/X.Y.Z/SHA256SUMS
curl -fLO https://agentgarm.com/download/X.Y.Z/SHA256SUMS.minisig
curl -fLO https://agentgarm.com/keys/release-feed.pub
foreach ($f in "download/X.Y.Z/SHA256SUMS", "download/X.Y.Z/SHA256SUMS.minisig", "keys/release-feed.pub") {
  Invoke-WebRequest "https://agentgarm.com/$f" -OutFile (Split-Path $f -Leaf)
}

2. Check the signature

With minisign:

minisign -Vm SHA256SUMS -p release-feed.pub

3. Check your file

shasum -a 256 -c SHA256SUMS --ignore-missing
sha256sum -c SHA256SUMS --ignore-missing
(Get-FileHash .\agentgarm-X.Y.Z-x86_64-pc-windows-msvc.msi -Algorithm SHA256).Hash.ToLower()
Select-String -Path .\SHA256SUMS -SimpleMatch "agentgarm-X.Y.Z-x86_64-pc-windows-msvc.msi"

The two hashes must be the same. If either check fails, do not run the file, and tell us.