Verify a download
Verify a published download checksum and pinned release signature locally without uploading your installer.
On this page
What the signature tells you
The SHA-256 detects a file mismatch. The detached Ed25519 signature binds that digest to the enrolled TraceForge release key. This is separate from Windows Authenticode, SmartScreen reputation and any engineering validation. Do not ignore an unexplained operating-system warning.
For the simple checksum check, see installation. The steps below additionally verify the release signature locally. Your installer is not uploaded anywhere.
Download the three files
From Downloads, obtain the installer and its Download signature JSON file. Also download the small verification script from this site. Keep all three in one folder and keep their original filenames.
The verifier pins the enrolled release public key internally rather than trusting a key supplied by the signature document. You can inspect the script as text before running it. The current key identifier is 477c2401bb8ff4338ae6e30d8f21d981; historic releases may require their historic verifier and key.
Run verification on Windows
This optional command-line check requires Python 3 and the cryptography library. If you already have a controlled Python environment, use it. Otherwise, use an isolated environment rather than changing your application installation:
py -m venv verify-env
.\verify-env\Scripts\python.exe -m pip install cryptography
.\verify-env\Scripts\python.exe .\verify-download.py .\TraceForge-0.1.5-windows-x64.exe .\TraceForge-0.1.5-windows-x64.exe.sig.json
Run the commands from the folder containing the downloaded files, substituting the exact filenames offered for your release. The verifier supports both the older public signature format and the current customer-package signature. Linux public 0.1.5 uses .tar.gz archives with .sig.json download signatures and a separate native-installer signature. Prepared 0.1.6 uses .deb and .deb.signature.json; do not use one release's instructions for the other. Installation of the optional verification dependency uses your configured Python package index. The verification script makes no network requests and never launches the installer.
Interpret the result
Signature and SHA-256 verified means the bytes match the signed release and its pinned key. It does not mean a circuit made with the application is safe, or that Windows must trust the publisher.
Verification FAILED means stop. Check that the signature is for the same filename and release. Download again from the canonical page. Do not edit the signature JSON, bypass the key check or rename an unrelated file to make the test pass.
If Python is unavailable or your environment prohibits installing its verification dependency, use the checksum comparison and contact support for the appropriate release verification path before proceeding when uncertain. Do not upload the installer or private files to an unknown checking service.