package signing
The use of cryptographic signatures on packages or repository metadata so a package manager can reject software that did not come from a trusted publisher.
Adding an unsigned or wrongly trusted repository lets whoever controls it install code as root.
In more detail
The distribution signs its repository index with a private key, and your machine holds the matching public key. Before installing, the package manager checks the signature and the checksums the index lists for each package. Signing proves where software came from and that it was not altered; it does not prove the software is correct or safe to run.
Related terms
- package repository — A server that a package manager downloads software packages from.
- package manager — A tool that installs, updates and removes software together with what it depends on, such as apt on Debian, apk on Alpine or Homebrew on macOS.
- digital signature — A value computed from data and a secret key that lets anyone with the matching verification key confirm the data came from the key holder and was not changed.
- public key — The shareable half of a key pair, used by others to verify your signatures or encrypt data only you can read.
Taught in
- What A Distribution Actually Is — Linux Fundamentals & Systems Administration
- What A Package Manager Guarantees — Linux Fundamentals & Systems Administration