d0ea790c6a
Declare the whole keyring data as well as the code as input dependency for the build target. This way we can properly depend on the build target for installation without forcing rebuilding on every invocation. A rebuild will be triggered if either the keyring or the source code creating the build output changes. The directories are added to the source dependencies on purpose to guarantee that changes like deleted files will result in a rebuild. The mtime of the build directory is force updated on every run to allow make to track the output artifacts mtime compared against the dependencies. |
||
|---|---|---|
| .gitlab | ||
| libkeyringctl | ||
| master | ||
| master-revoked | ||
| packager | ||
| packager-revoked | ||
| tests | ||
| .editorconfig | ||
| .flake8 | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| archlinux-revoked | ||
| archlinux-trusted | ||
| archlinux.gpg | ||
| CONTRIBUTING.md | ||
| keyringctl | ||
| LICENSE | ||
| Makefile | ||
| master-keyids | ||
| master-revoked-keyids | ||
| packager-keyids | ||
| packager-revoked-keyids | ||
| pyproject.toml | ||
| README.md | ||
| update-keys | ||
archlinux-keyring
The archlinux-keyring project holds PGP packet material and tooling
(keyringctl) to create the distribution keyring for Arch Linux.
The keyring is used by pacman to establish the web of trust for the packagers
of the distribution.
The PGP packets describing the main signing keys can be found below the keyring/main directory, while those of the packagers are located below the keyring/packager directory.
Requirements
The following packages need to be installed to be able to create a PGP keyring from the provided data structure and to install it:
Build:
- make
- findutils
Runtime:
- python
- sequoia-sq
Optional:
- hopenpgp-tools (verify)
- sq-keyring-linter (verify)
- git (ci)
Usage
Build
Build all PGP artifacts (keyring, ownertrust, revoked files) to the build directory
./keyringctl build
Import
Import a new packager key by deriving the username from the filename.
./keyringctl import <username>.asc
Alternatively import a file or directory and override the username
./keyringctl import --name <username> <file_or_directory...>
Updates to existing keys will automatically derive the username from the known fingerprint.
./keyringctl import <file_or_directory...>
Main key imports support the same options plus a mandatory --main
./keyringctl import --main <username>.asc
Export
Export the whole keyring including main and packager to stdout
./keyringctl export
Limit to specific certs using an output file
./keyringctl export <username_or_fingerprint_or_directory...> --output <filename>
List
List all certificates in the keyring
./keyringctl list
Only show a specific main key
./keyringctl list --main <username_or_fingerprint...>
Inspect
Inspect all certificates in the keyring
./keyringctl inspect
Only inspect a specific main key
./keyringctl inspect --main <username_or_fingerprint_or_directory...>
Verify
Verify certificates against modern expectations and assumptions
./keyringctl verify <username_or_fingerprint_or_directory...>
Installation
To install archlinux-keyring system-wide use the included Makefile:
make install
Contribute
Read our contributing guide to learn more about guidelines and how to provide fixes or improvements for the code base.
Releases
Releases of
archlinux-keyring
are created by its current maintainer Christian
Hesse. Tags are signed using the PGP key
with the ID 02FD1C7A934E614545849F19A6234074498E9CEE.
To verify a tag, first import the relevant PGP key:
gpg --auto-key-locate wkd --search-keys eworm@archlinux.org
Afterwards a tag can be verified from a clone of this repository:
git verify-tag <tag>
License
Archlinux-keyring is licensed under the terms of the GPL-3.0-or-later (see LICENSE).