This is the original walkthrough, kept for reference. Software and services have changed since it was written. Read the current guide.
This illustrated walkthrough includes older software and hardware. Its screenshots explain the workflow, but menu names, prices, requirements and service availability may differ. Use the linked project documentation for the version you are running.
Verifying software sounds like a really scary thing that only ‘technical people’ do, which is the exact reason that until very recently, I didn’t bother either!
“I’ve never had a problem before, so why should I start now?”
An app store may check distribution and enforce platform rules, but its listing is not proof that an app is trustworthy or bug-free. Verify the publisher and follow the project’s release-verification guidance where available.
What happens if you don’t verify your software? Most of the time nothing at all. Other times, malicious software can infect your computer with malware that looks identical to the software you expect to see, but could be built to steal every sat you possess. This software could be the interface through which you interact with your life savings. Five minutes following this guide seems like a worthwhile investment now doesn’t it?
BASIC CONCEPTS
Some of the basic concepts and terminology used here may be familiar to those in Bitcoin. The principles and the way they work in relation to software is the same.
Private Key - A secret known only to its owner. It can be used to sign files or messages
Public Key - A publicly shareable ID that can be used to validate that a message or signature has come from its corresponding private key.
Signature - Provided by the private key as a type of proof which can be confirmed using the corresponding public key.
SHA256 - A function which, when performed on any file will produce a string of letters and numbers as an output. This output can be compared with other produced outputs to verify the contents of the file are an exact match.
Verifying Specter Desktop
Use the current Specter release and signing instructions rather than copying an old filename or key identifier. Verify both the signature and the installer’s digest. A valid signature ties a file to a key; independently checking that key’s identity remains part of the process.
The process is the same on Linux and macOS, but the hash command can differ. Linux commonly provides sha256sum; macOS provides shasum -a 256. GPG verification uses the matching signature and signed file on either system. The old Specter 1.0.0 filenames below are an example, not a current download recommendation.
1.Download the latest version of Specter Desktop relevant to your computer’s operating system. Then download the sha256.signed.txt file to your downloads folder.
FIG. 01Verifying Specter Desktop
Specter v2.1.11 publishes a signed SHA256SUMS file using the Specter Signer 2026 key, fingerprint 9DC3 3CA8 3058 9DE3 B322 5C26 EEF5 756B 2EA4 2349. Authenticate that full fingerprint through the official release instructions, import the corresponding key and verify the signed manifest before comparing the installer's hash. The old Stepan key and v1.0.0 filenames below belong to the historical example.
FIG. 02Verifying Specter Desktop
A public key's name and email are self-asserted. Compare its full fingerprint with authenticated project channels, preferably through an independent channel you already trust. A fingerprint identifies key material; finding the same display name in a keyserver search does not establish that the key belongs to the developer.
Another way to obtain a public key is from a publicly posted PGP block like mine. Simply save the entire block as a text file onto your computer.
3. Now we need to import that public key into your computer’s key chain so it can use it as a reference in the steps that follow. Open your downloads folder, right click and then “open in terminal”. In the terminal, type the command below.
gpg --import ss-specter-release.asc
FIG. 03Verifying Specter Desktop
Side note - If using this guide for different software or have imported the key using a text file then you should modify the file part of the command above to suit the file name you gave.
Pro Tip - Once you start typing a filename in terminal, pressing the tab button should auto complete for you.
4. Now we need to make sure that the signed release was actually signed by the person we think it was. The command below will check that the signature in the sha256.signed.txt file we downloaded in step 1 came from Stepan’s key which we imported in step 3.
Depending on the software you are downloading, some projects will provide a .sig file instead of a .txt file but the principle is identical.
gpg --verify sha256.signed.txt
FIG. 04Verifying Specter Desktop
Note the Good signature from Stepan Snigirev. We can now be confident that the file we downloaded in step 1 is signed by Stepan with his private key.
5. Finally, we need to ensure the contents of the file signed by Stepan are the exact same as the contents of the file we downloaded. Run the following command.
sha256sum specter_desktop-v1.0.0-x86_64-linux-gnu.tar.gz
FIG. 05Verifying Specter Desktop
When we compare the output from the command above with the publicly shared SHA256 hash file below, we get an exact match (see line 6). This means that the contents of the file we have downloaded are an exact match to the one the developers have signed for release.
FIG. 06Verifying Specter Desktop
Had there have been one single byte of data different in the file we downloaded, compared with the one Stepan signed, the output from step 5 would look completely different and would suggest that something is wrong. In this scenario you should reach out to the developer team.
It might seem like a pain to verify software, particularly if there are regular releases. But think of the potential risks of not doing this. It only takes one piece of malicious software for a successful attack.
This guide used Specter Desktop as an example, but all open source software should follow an almost identical path.
Remember…
Import the verified release key when needed, and recheck it when the project announces a rotation or your verification reports a different key. For every new download, verify the corresponding signature and installer hash again.
- Check the signature came from that developers key
- Check the contents of the file match the contents of the file the developer produced
If you need help getting started with software verification, I offer private support calls for those that benefit from more personalised tuition.
