Package signature checks split into metadata trust and payload trust
A signed package can arrive through a repository whose index was not authenticated. An authenticated repository index can point to a package whose local signature policy is weak. APT and RPM expose different parts of this chain, and a review that treats "the key is installed" as the whole control will miss the gap between them.
APT authenticates repository metadata through the Release file and its signatures. The repository publishes a Release file, and the package indexes are covered by hashes in that release. The signed-by option narrows which keys can authenticate a particular source. A source marked trusted=yes is allowed to bypass authentication. Valid-Until and related date checks prevent a stale release from looking current.
The RPM package format carries OpenPGP signatures and digests over the package header and payload.…