Verify GPG signatures on downloaded files
Prove a release file really came from the developer and was not modified in transit.
01Command
$ gpg --verify program.tar.gz.sig program.tar.gz02What it does
A detached signature (.sig/.asc) is a cryptographic fingerprint of the exact file, encrypted with the developer's private key. gpg --verify re-computes the fingerprint with the public key from your keyring and reports whether the file matches and who signed it. The typical flow: gpg --recv-keys <KEYID> or import a key file, then verify the signature, then optionally verify that key's fingerprint against the value published on the project's site.
03Risk
04Undo
✓No undo needed — this command does not change persistent state.
05Sources
- gpg(1) - Ubuntu manpageEvidence: Same gpg manual: --verify verifies signatures, --list-keys lists the keyring needed to make verification meaningful.
- gpg(1) — Arch Manual PagesEvidence: Documents --verify (check a signature against a file), --list-keys and --detach-sign for detached signature workflows.
Last verified: 2026-09-19 · Category: Security & Privacy
06Related solutions
Generate a modern Ed25519 public/private key pair in ~/.ssh for authenticating to servers and Git platforms without passwords.
Add or remove read, write, and execute permission for the owner, group, or others using symbolic or octal modes.
Add a UFW rule to permit inbound traffic on a TCP or UDP port, such as SSH on port 22.