Before you start
- Use a test system and a known distribution release. Read the existing trust configuration and keep package verification enabled.
- Record the distribution release and the exact repository or package. Use the publisher's own documentation to confirm the expected signing key.
Data and access
Ubuntu
Read the APT source entry for the Ubuntu archive. Check its Signed-By field for the archive keyring, or check the distribution's trusted keyring if the field is absent. Refresh APT's package lists on the test system and check the result for that exact source. APT verifies the signed release metadata and uses the hashes it contains to verify what it downloads.
Check. The configured Ubuntu source refreshes without a signature error using the expected archive trust configuration.
Debian
In the APT source entry, inspect the key named or embedded by Signed-By. Refresh the package lists and check for a signature error on that source. Debian's APT verification follows the signed repository metadata. A successful refresh establishes repository trust for the configured source and key.
Check. The exact Debian source refreshes without a signature error. Compare the configured signing key with the intended archive key.
Red Hat Enterprise Linux
On a test system, compare the trusted key with Red Hat's published fingerprint for the product and release. Run rpmkeys --checksig on one downloaded Red Hat RPM without installing it. Use verbose output to check the signature and digests and confirm the expected signer.
rpmkeys --checksig --verbose package.rpmCheck. The downloaded RPM passes the signature and digest checks, and the key matches the expected Red Hat product key.
Record what you verified
Save the exact source or filename, distribution release, expected signing-key fingerprint and verification result. Repository metadata and an individual package signature are different records. Note which one you checked.
Check. Your record names the exact archive source or RPM and identifies the type of verification it passed.
Check your result
The check corresponds to the intended package or source and to the signing key documented for that release.
If you get stuck
The signing key was missing or unexpected
Review the exact source, distribution release and publisher fingerprint against the distribution's documentation. Check whether the installed distribution keyring is current, and resolve the discrepancy before installing the package.