Before opening an installer, flashing firmware, or deploying a release, use this practical checklist to verify that the file you received matches the publisher’s intended file. It explains what checksums, digital signatures, signed checksum files, and supply-chain attestations can—and cannot—prove, with copyable verification steps for Windows, macOS, and Linux.
Overview
Download verification has two separate goals: checking integrity and checking authenticity. A cryptographic hash such as SHA-256 or BLAKE3 produces a fingerprint for a file. If your calculated fingerprint matches a value published by a trusted source, you have evidence that the file contents are unchanged since that value was produced.
A matching hash does not, by itself, prove who created the file. An attacker who can replace a download may also be able to replace an unsigned checksum displayed beside it. Authenticity requires a trusted distribution channel, a digital signature, or a stronger release-verification process in which the checksum or provenance statement is itself protected.
Use the following hierarchy as a starting point:
- Trusted package manager or repository: useful when the repository’s metadata, transport, and signing model are part of your trust decision.
- Published checksum: confirms that your copy matches the published value, provided you obtained that value through a trustworthy channel.
- Digital signature: verifies that a file or manifest was signed by a key whose identity and validity you have checked.
- Signed checksums or attestations: can link release files to a signed manifest, build process, source revision, or workflow identity.
| Method | What it checks | Main limitation | Best use |
|---|---|---|---|
| SHA-256 | Whether file contents match a known digest | Does not identify the publisher if the digest is unauthenticated | General-purpose release and image verification |
| SHA-512 | Whether contents match a longer digest | Same trust limitation as other unsigned hashes | Projects that publish SHA-512 as their standard |
| BLAKE3 | Whether contents match a BLAKE3 digest | Requires compatible tooling and publisher support | Fast local verification where the release process uses it |
| Digital signature | Whether a recognised key signed the file or manifest | Key trust, expiry, revocation, and scope still need checking | Installers, packages, manifests, and release archives |
| Signed checksum file | Whether a signed manifest lists the expected file digest | Does not prove the build was free from compromise | Verifying several release assets together |
| Supply-chain attestation | Claims about source, builder, workflow, or provenance | Meaning depends on the attestation format and trusted identities | Higher-assurance software release and deployment workflows |
Checklist by scenario
Downloading an installer or release archive
- Start at the publisher’s official website or documented repository. Avoid relying on a search result, forum attachment, or reposted mirror when a primary source is available.
- Record the exact filename, version, platform, and architecture. A correct hash for a different build is not a valid verification.
- Look for a checksum, signature, signed manifest, or documented package-manager command. Prefer a verification method described by the publisher rather than an improvised one.
- Calculate the digest locally and compare the complete value. Do not treat a shortened prefix as sufficient unless the publisher explicitly defines that process.
- If a signature is available, validate both the signature and the signing key’s identity through an independent trusted channel.
- Keep a record of the URL, version, digest, verification result, and date for software that will be deployed widely.
Windows
PowerShell includes a built-in command for common hash algorithms:
Get-FileHash .\installer.exe -Algorithm SHA256
For SHA-512, change the algorithm:
Get-FileHash .\installer.exe -Algorithm SHA512
Compare the returned Hash value with the publisher’s complete value, ignoring differences in capitalisation but not differences in characters. For a Windows executable with an Authenticode signature, you can inspect the signature status with:
Get-AuthenticodeSignature .\installer.exe
A valid status is only one part of the review. Check the signer information, confirm that it is the expected publisher, and consider whether the certificate is appropriate for that software.
macOS
For SHA-256:
shasum -a 256 ~/Downloads/application.dmg
For SHA-512:
shasum -a 512 ~/Downloads/application.dmg
macOS also provides:
openssl dgst -sha256 ~/Downloads/application.dmg
To inspect an application’s code signature, use the application bundle path:
codesign --verify --deep --strict --verbose=2 /Applications/Application.app
Where relevant, review the developer identity and notarisation information using Apple’s documented security tools. A successful local command does not replace checking that the application came from the expected publisher.
Linux
For SHA-256:
sha256sum ./release.tar.gz
For SHA-512:
sha512sum ./release.tar.gz
If the publisher supplies a checksum file in a compatible format, you may be able to verify it directly:
sha256sum --check SHA256SUMS
For a detached OpenPGP signature, the general pattern is:
gpg --verify SHA256SUMS.sig SHA256SUMS
Read the result carefully. A signature can be mathematically valid while the key is not the publisher’s confirmed key. Check the fingerprint using a separate trusted source before treating the result as an identity confirmation.
Installing through a package manager
Package managers often provide repository metadata, dependency resolution, and their own verification behaviour. Use the package manager’s official documentation and configured repositories rather than downloading a package from an unrelated file host. Before deployment, review the repository source, package name, version, architecture, and any available signature or provenance information. In controlled environments, pin approved repositories and retain package records so that a later investigation can reconstruct what was installed.
What to double-check
- The comparison source: A checksum copied from the same untrusted location as the file offers weaker protection than one obtained from a separate publisher-controlled channel.
- The exact asset: Operating-system images, installers, debug builds, source archives, and container images can all have different hashes. Match filename, version, platform, and architecture.
- Signature identity: Confirm the key fingerprint, certificate subject, or signing identity—not merely that a tool reports a valid signature.
- Signing scope: Determine whether the signature covers the executable, the archive, a checksum manifest, or a provenance statement. These are not interchangeable.
- File handling: Repacked archives, line-ending conversions, extraction and recompression change hashes. Verify the original downloaded file before modifying it.
- Warnings and failures: A mismatch, unknown key, expired certificate, revoked key, or failed signature should pause the installation. Downloading the file again is reasonable; ignoring the result is not.
- Build provenance: For sensitive production software, ask whether the release is linked to a source revision, reproducible build, trusted builder, or signed attestation. Treat provenance as additional evidence, not as a substitute for understanding the release process.
Common mistakes
Confusing hashing with encryption. A SHA-256 digest is not a secret and cannot be used to decrypt a file. It is a fixed-length representation used for comparison.
Assuming a hash proves authenticity. Hashes detect changes relative to a trusted reference. They do not independently prove who produced either the file or the reference.
Checking only a few characters. Visual comparison of a full digest is safer than checking a short prefix. For automation, compare exact values and fail closed on a mismatch.
Trusting a valid signature without checking the key. Signature validation answers whether a particular key signed the data. It does not automatically answer whether that key belongs to the expected publisher.
Using a web-based hash generator for confidential files. Uploading a proprietary installer, firmware image, source bundle, or customer data to an online tool may disclose sensitive information. Prefer local command-line tools or approved internal utilities.
Skipping verification because the download uses HTTPS. HTTPS protects the connection to a server but does not replace release-level verification. Use both where the software’s risk justifies it.
Automating installation before verification. Download, verify, scan or inspect according to policy, and only then execute or deploy. Keep temporary downloads separate from trusted software directories.
When to revisit
Use this checklist every time you download a new operating-system image, installer, firmware package, recovery medium, dependency, container image, or developer release. Revisit your documented procedure before seasonal planning cycles, platform migrations, and large software rollouts, especially when an operating system changes its built-in tools or a package manager changes its repository behaviour.
Developers and IT administrators should also review the process when changing CI/CD providers, signing keys, build runners, release formats, artifact repositories, or provenance tooling. A command that worked for a local archive may not verify a container image or a signed package correctly.
For a practical release gate, assign an owner and record these fields:
- Product, version, filename, platform, and architecture
- Download location and date
- Expected and calculated digest, including the algorithm
- Signature or attestation result and verified signer identity
- Approver, deployment scope, and any exceptions
If a file fails verification, stop the workflow, preserve the original download and relevant logs, and contact the publisher through a known-good channel. Do not disable security controls or substitute an unverified mirror simply to keep a release moving. When the tools or workflow change, run the verification process against a test release first, update the internal runbook, and then use the revised procedure for production files.