This page covers usage of package signing with Pacman, as well as being a brain dump and collaborative design document.
See also: Package Signing Proposal for Pacman
Pacman 4 uses GnuPG to implement package signing.
- 1 Usage
- 2 Course of action for development
- 3 How signing is implemented in other distributions
- 4 Links
- Packages are signed using
makepkg --sign. This creates a detached binary signature (.sig).
- The signed package is added to the repository database, and a detached signature of the repository database will be generated, using
repo-add --verify --sign. The command line options indicate that the signature of the old database will be verified, and that the new database will be signed. Independently of these options,
repo-addwill detect the detached signature, convert it via base64 to ASCII, and add it to the repository database.
pacmanwill download both the databases and the database signatures and verify the databases upon database sync and each time the database is opened. When a package is loaded, its signature will be checked whether that comes from a repo database or a standalone .sig file.
pacman-keyexists for the sake of managing keys, but there is missing functionality
To prepare for checking signed packages, run the pacman-key command shown below, with root permissions. It generates a random key and a “keyring” in /etc/pacman.d/gnupg/. You may need to move the mouse around to generate entropy for the key.
# pacman-key --init
If this command is never run, Pacman will abort saying “failed to commit transaction (invalid or corrupted package [PGP signature])” when it encounters packages signed with an unknown key.
By default, Pacman automatically accepts unsigned packages, but signed ones are rejected with an error unless the Pacman considers the key to be “trusted”. This corresponds to “SigLevel = Optional” in pacman.conf; see “Package and database signature checking” in the pacman.conf man page for further information.
Pacman usually prompts to add new keys of signed packages to its keyring. Keys can be manually compared against the lists of Arch developers and trusted users on the Arch Linux web site. If the SigLevel configuration specifies “TrustAll”, Pacman considers keys to be trusted once they are imported to the keyring, so it will then continue installing each package. If Pacman does not prompt to add new keys (cannot find on configured key server perhaps?), they could still be added manually by using the pacman-key tool.
If SigLevel specifies TrustedOnly (the default), Pacman also considers the “trust level” for each key. A key is considered trusted if it is locally signed, or it has a sufficient level in the Pacman web of trust. Locally signing a key (with “pacman-key --lsign”) only really works after the key has already been imported.
If there is a long time and failure right after checking packages integrity, edit “/etc/pacman.d/gnupg/gpg.conf” to use a different key server, for example “keyserver hkp://pgp.mit.edu” instead of keys.gnupg.net.
Course of action for development
These are the changes that need to be made before Arch can implement package signing.
Some package will be created that contains all necessary keys for an Arch user to validate package signatures.
The DeveloperWiki page for key creation must be finalized. Several developers and now Kerrick are working on this; feel free to contribute.
Key creation, submission and verification
Solely the responsibility of the developers. This page gives the current progress.
pactests must be written for all signing functionality. This is a big issue; if you would like to contribute, this is a good place to do so.
Documentation for the new features must be reviewed and finalized.
These are important but non-essential features that should be added soon after package signing is implemented. Work on these issues can start now, but priority should be given to the "requirements" above.
Package validation without root privileges
Currently, pacman's GnuPG home directory (aka gpgdir, typically /etc/pacman.d/gnupg/) must be locked in order to check a package's signature. Only root can perform this locking, so either locking must be disabled for read-only accesses, or the directory must be copied/linked to a writable location when a user is performing package verification.
Timeline for increasing security
A timeline for transitioning between some unsigned packages and a fully-signed set of packages must be made. This is the responsibility of the developers.
Allan's TODO list
Allan has a TODO list with further needed features at User:Allan/Package Signing.
How signing is implemented in other distributions
Frugalware uses a fork of pacman which implements package signing (verify)
Arch based distro gnuffy uses signed packages with their custom package manager Spaceman modeled on pacman.
Binary packages (.deb)
To sum up, the GPG signature is included in the .deb.
Regular non signed binary packages are "ar" archives of at least 3 files:
- data.tar.gz (files to be installed)
- control.tar.gz (package metadata)
- debian-binary (contains the version of the deb format)
Signed packages also have a _gpgorigin file at the root of the .deb that is a "gpg -abs" of the concatenation of the 3 laters (as explained here):
cat debian-binary control.tar.gz data.tar.gz > /tmp/combined-contents gpg -abs -o _gpgorigin /tmp/combined-contents (-a "Create ASCII armored output" ; -b "detach signature" ; -s "sign")
Original files are provided on the repo like this acpid_2.0.4.orig.tar.gz with diff if necessary (acpid_2.0.4-1.diff.gz). A description file containing MD5sums of the orig.tar.gz and diff.gz is written and signed using GPG and uploaded along these.
- Signature type: GPG
- Stored: in the RPM
A RPM package is a tarball of installed files to which is added a header made up of metadata (name of package, version, ...). This metadata can contain a GPG signature of the tarball. See the file format specification for details.
NB: packages built for the RedHat Network are signed with the RedHat official key(s) but technically a RPM can be signed using any other key (one can even add another signature to the RPM)
To check a package correction, one must first import the signer's key first: Example for RedHat
rpm --import /usr/share/doc/rpm-4.1/RPM-GPG-KEY
And can then check signature manually:
$ rpm -K openldap-clients-2.3.43-4.x86_64.rpm openldap-clients-2.3.43-4.x86_64.rpm: sha1 md5 OK
And even fully check the package (MD5):
$ rpm -Kv openldap-clients-2.3.43-4.x86_64.rpm openldap-clients-2.3.43-4.x86_64.rpm: SHA1 header hash: OK (65999383ad859be0ce337aee4c1f6bd049ebe4a0) MD5 sum: OK (4be23a341d23b794d08fbee35c459c83)
Option --nogpg prevents rpm from checking GPG signatures
- Enable Official Distribution package signature but also enables personal and multiple signatures
- Implies complicated package format with header containing signature of an inner tarball (not very KISS)
- Space greedy on repos
For each package, a small description file containing the SHA sum of the package is created. That file is then signed using gpg (.dsc) and uploaded within the same folder as the package:
gpg --clearsign description_of_package
- Space greedy (2 files for 1 package)
Mailing list discussions and patches
- Add Keyring option in alpm/pacman
- Package signing again
- PATCH (newgpg) Let pacman specify GnuPG's home directory.
- Dan's pacman tree build&test
- GPG work
- GPG signature option in makepkg patch
- GPG signature support for makepkg
- GPG signature option in makepkg, adapted to Dan McGee's suggestions patch
- GPG verification patch
- GPGSIG in repo-add patch
- Signing by default
- Package Database signing
- Pointless to use non-md5 for makepkg INTEGRITY_CHECK
- Can we trust our mirrors
- Multiple/Shared Architectures