Verifying Integrity
Verify a manually downloaded agent before using it. Each version-specific release page publishes checksums for each supported architecture.
WARNING
MD5 checksums are provided for compatibility with older systems and workflows. Use SHA-256 as the primary integrity validation algorithm when it is available.
Get the published checksum
Open the Agent Releases page:
Select the downloaded version.
Locate the checksums for the selected architecture.
Copy the published SHA-256 value. If SHA-256 is not available for the target system or workflow, copy the MD5 value.
Validate with SHA-256
Run the following command in the directory that contains the downloaded agent file:
sha256sum ./agentCompare the output with the SHA-256 value published on the release page for the selected version and architecture.
You can also validate the file by using sha256sum --check:
echo "<published-sha256> ./agent" | sha256sum --checkReplace <published-sha256> with the SHA-256 value from the release page.
If the command returns OK, the local file matches the published checksum.
Validate with MD5
Use MD5 only when SHA-256 validation is not available for the target system or workflow.
Run the following command in the directory that contains the downloaded agent file:
md5sum ./agentCompare the output with the MD5 value published on the release page for the selected version and architecture.
You can also validate the file by using md5sum --check:
echo "<published-md5> ./agent" | md5sum --checkReplace <published-md5> with the MD5 value from the release page.
If the command returns OK, the local file matches the published checksum.
Validation failures
If the calculated checksum does not match the published checksum, do not use the downloaded file.
Download the file again and repeat the validation. If the checksum still does not match, contact Mutexer Support and include the agent version, selected architecture, calculated checksum, and published checksum.