.editorconfig

 root = true
+
 [*]
 end_of_line = lf
 charset = utf-8
+indent_style = space
+indent_size = 4
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[Makefile]
+end_of_line = lf
+charset = utf-8
 indent_style = tab
-indent_size = 8
+indent_size = 4
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[{*.py,keyringctl}]
+indent_style = space
+indent_size = 4
+max_line_length = 120
+
+[*.{yml,yaml}]
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+charset = utf-8
+indent_style = space
+indent_size = 2

.flake8

+[flake8]
+max-line-length = 120
+output-file = flake8.txt
+max-complexity = 10

.gitattributes

-update-keys	export-ignore
-.gitattributes	export-ignore
-.gitignore	export-ignore
-master-keyids	export-ignore
-packager-keyids	export-ignore
-master		export-ignore
-packager	export-ignore
-.editorconfig	export-ignore
-master-revoked-keyids	export-ignore
-master-revoked	export-ignore
-packager-revoked-keyids	export-ignore
-packager-revoked	export-ignore

.gitignore

+/build
 *~
 archlinux-keyring-*.tar.gz
 archlinux-keyring-*.tar.gz.sig
 /.idea
+.coverage
+__pycache__/

.gitlab-ci.yml

+---
+image: archlinux:latest
+
+stages:
+  - test
+  - wkd
+
+lint:
+  stage: test
+  needs: []
+  before_script:
+    - pacman-key --init
+    - pacman -Syu --needed --noconfirm make flake8 mypy python-black python-isort
+  script:
+    - make lint
+  only:
+    changes:
+      - keyringctl
+      - libkeyringctl/*
+      - tests/*
+      - .gitlab-ci.yml
+      - Makefile
+
+test:
+  stage: test
+  needs: []
+  before_script:
+    - pacman-key --init
+    - pacman -Syu --needed --noconfirm make python sequoia-sq python-coverage python-pytest python-tomli wkd-exporter
+  script:
+    - make test
+    - make wkd
+    - make wkd WKD_FQDN=master-key.archlinux.org
+    - make wkd_inspect
+    - make wkd_inspect WKD_FQDN=master-key.archlinux.org
+  only:
+    changes:
+      - keyringctl
+      - libkeyringctl/*
+      - tests/*
+      - .gitlab-ci.yml
+      - Makefile
+  coverage: '/TOTAL.*\s([.\d]+)%/'
+  artifacts:
+    when: always
+    reports:
+      coverage_report:
+        coverage_format: cobertura
+        path: build/coverage.xml
+      junit: build/junit-report.xml
+
+build_install:
+  stage: test
+  needs: []
+  before_script:
+    - pacman-key --init
+    - pacman -Syu --needed --noconfirm make pkgconf python sequoia-sq systemd
+  script:
+    - make
+    - make install PREFIX=/usr
+
+keyring_check:
+  stage: test
+  needs: []
+  before_script:
+    - pacman-key --init
+    - pacman -Syu --needed --noconfirm make python sequoia-sq git
+  script:
+    - ./keyringctl check
+    - ./keyringctl ci
+  only:
+    changes:
+      - keyring/**/*
+      - keyringctl
+      - libkeyringctl/*
+      - tests/*
+      - .gitlab-ci.yml
+      - Makefile
+
+pages:
+  stage: wkd
+  needs: []
+  tags:
+    - secure
+  before_script:
+    - pacman-key --init
+    - pacman -Syu --needed --noconfirm make python sequoia-sq wkd-exporter
+  script:
+    - make wkd
+    - make wkd WKD_FQDN=master-key.archlinux.org
+    - make wkd_inspect
+    - make wkd_inspect WKD_FQDN=master-key.archlinux.org
+    - cp -r build/wkd/ public
+  artifacts:
+    paths:
+      - public
+  rules:
+    - if: $CI_PROJECT_PATH == "archlinux/archlinux-keyring" && $CI_COMMIT_TAG

.gitlab/CODEOWNERS

+* @archlinux/teams/main-key-holders

.gitlab/issue_templates/New Main Key.md

+<!--
+This template is used when a new main PGP public key needs to be added to the distribution's keyring.
+It is used by users with a valid packager key.
+
+NOTE: All comment sections with a MODIFY note need to be edited.
+      All checkboxes in the "Checks" section labeled as "Owner of new key" need to be checked by the owner of the new key.
+-->
+
+/assign @archlinux/teams/main-key-holders
+/label ~"new main key"
+/title New main key of <!-- MODIFY: Add new main key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Add a new main key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the output of `gpg --keyid-format long --list-key <MY UID> | sed -n '2p' | tr -d ' '` here -->
+- Revocation Certificate Holder: <!-- MODIFY: Add the @-prefixed username of the revocation certificate holder -->
+
+<!--
+MODIFY: Attach the above information of the details section as a clearsigned document (see https://www.gnupg.org/gph/en/manual/x135.html) to this ticket using a valid packager key of the user:
+
+* Select the above text, copy/paste it into a file (e.g. `details.txt`).
+* Make sure to sign with the root certificate of the packager key (not any of the subkeys!): `gpg --armor --default-key <fingerprint_of_root>! --clearsign details.txt`
+* Upload `details.txt` as attachment to this ticket.
+-->
+
+## Checks
+
+**NOTE**: The below check boxes **must be** checked before the accompanying merge request to add the new main key can be merged.
+
+### Owner of new key
+
+- [ ] The [workflow for adding a new main key] has been followed
+- [ ] The key pair has been validated according to the [best practices]
+- [ ] The data in the [Details] section is attached to this issue as a clearsigned document
+- [ ] The revocation certificate has been sent in an encrypted message to the revocation certificate holder
+- [ ] The public key has been uploaded to the `keyserver.ubuntu.com` and `keys.openpgp.org` keyservers, and the `archlinux.org` UID has been verified on the `keys.openpgp.org` keyserver.
+      Optionally the key can also be uploaded to the `pgp.mit.edu` keyserver, but this is no longer mandatory as it's frequently flaky.
+- [ ] A merge request to add the new public key has been created
+
+### Revocation Certificate Holder
+
+- [ ] The revocation certificate has been [verified as working] and confirmed in a comment to this issue
+- [ ] The revocation certificate has been backed up on a dedicated encrypted backup storage medium
+
+### Main key holders
+
+- [ ] The data in the [Details](#details) section is correct and signed with a valid and trusted packager key, which is already part of `archlinux-keyring`
+
+[workflow for adding a new main key]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-main-key
+[best practices]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
+[Details]: #details
+[verified as working]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/verify-a-revocation-certificate

.gitlab/issue_templates/New Packager Key.md

+<!--
+This template is used when a new packager PGP public key needs to be added to the distribution's keyring.
+It is either used by the sponsor of a new packager or by an existing packager when adding a new key for themself.
+
+NOTE: All comment sections with a MODIFY note need to be edited.
+      All checkboxes in the "Checks" section labeled as "Owner of new key" need to be checked by the owner of the new key or by a sponsor of a new packager.
+-->
+
+/assign @archlinux/teams/main-key-holders
+/label ~"new packager key"
+/title New packager key of <!-- MODIFY: Add new packager key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Add a new packager key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the output of `gpg --keyid-format long --list-key <MY UID> | sed -n '2p' | tr -d ' '` here -->
+- Sponsors: <!-- MODIFY: Add the @-prefixed usernames of the sponsors -->
+- Application: <!-- MODIFY: Add link to application, if this is the key of a new packager, else remove -->
+- Results: <!-- MODIFY: Add link to results of application, if this is the key of a new packager, else remove -->
+- Previous Key: <!-- MODIFY: Add the output of `gpg --keyid-format long --list-key <MY PREVIOUS ID> | sed -n '2p' | tr -d ' '` here if another packager key exists already, else remove -->
+
+<!--
+MODIFY: Attach the above information of the details section as a clearsigned document (see https://www.gnupg.org/gph/en/manual/x135.html) to this ticket.
+If a previous (valid and trusted) packager key of the user exists, it needs to be used for clearsigning the document.
+If the key of a new packager is added, one of their sponsors needs to clearsign the details section.
+
+* Select the above text, copy/paste it into a file (e.g. `details.txt`).
+* Make sure to sign with the root certificate of the packager key (not any of the subkeys!): `gpg --armor --default-key <fingerprint_of_root>! --clearsign details.txt`
+* Upload `details.txt` as attachment to this ticket.
+-->
+
+## Checks
+
+### Owner of new key
+
+- [ ] The [workflow for adding a new packager key] has been followed
+- [ ] The key pair contains one user ID with a valid `<username>@archlinux.org` email address used for signing
+- [ ] The key pair has been validated according to the [best practices]
+- [ ] The data in the [Details] section is attached to this issue as a clearsigned document
+- [ ] The public key has been uploaded to the `keyserver.ubuntu.com` and `keys.openpgp.org` keyservers, and the `archlinux.org` UID has been verified on the `keys.openpgp.org` keyserver.
+      Optionally the key can also be uploaded to the `pgp.mit.edu` keyserver, but this is no longer mandatory as it's frequently flaky.
+- [ ] A merge request to add the new public key has been created
+
+### Main key holders
+
+- [ ] The public key has been signed by all main key holders
+  - [ ] @anthraxx
+  - [ ] @artafinde
+  - [ ] @demize
+  - [ ] @dvzrv
+
+### Developers of the archlinux-keyring project
+- [ ] The data in the [Details] section is correct and signed with a valid and trusted packager key, which is already part of `archlinux-keyring`
+
+[workflow for adding a new main key]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-main-key
+[best practices]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair
+[Details]: #details
+[verified as working]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/verify-a-revocation-certificate

.gitlab/issue_templates/Remove Main Key.md

+<!--
+This template is used when an existing main PGP public key needs to be removed from the distribution's keyring.
+It is used by users with a valid main key or the holder of the revocation certificate of the main key that is about to be removed.
+
+NOTE: All comment sections with a MODIFY note need to be edited.
+      All checkboxes in the "Check" section labeled as "Main key holders" need to be checked for the accompanying merge request to be merged.
+-->
+
+/assign @archlinux/teams/main-key-holders
+/label ~"remove main key"
+/title Remove main key of <!-- MODIFY: Add main key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Remove a main key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the output of `gpg --keyid-format long --list-key <MAIN KEY UID> | sed -n '2p' | tr -d ' '` here -->
+- Resignation: <!-- MODIFY: Link to resignation of key holder -->
+
+## Checks
+
+### Main key holders
+
+- [ ] There are more than or equal to four valid main keys remaining after removal of this key.
+- [ ] All packagers have at least three valid main key signatures for their packager key after removal of this key.
+- [ ] A merge request to [remove the main public key] has been created
+
+[remove the main public key]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/remove-a-main-key 

.gitlab/issue_templates/Remove Packager Key.md

+<!--
+This template is used when an existing packager PGP public key needs to be removed from the distribution's keyring.
+It is used by users with a valid main key or a valid packager key.
+
+NOTE: All comment sections with a MODIFY note need to be edited.
+-->
+
+/assign @archlinux/teams/main-key-holders
+/label ~"remove packager key"
+/title Remove packager key of <!-- MODIFY: Add packager key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Remove a packager key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the output of `gpg --keyid-format long --list-key <PACKAGER KEY UID> | sed -n '2p' | tr -d ' '` here -->
+- Resignation: <!-- MODIFY: Link to resignation of key holder -->
+
+## Checks
+
+**NOTE**: The below check box **must be** checked before the main key holders can start to revoke the key.
+
+- [ ] There are [no packages left in any of the official repositories], that are signed by the key or any of its subkeys, which is about to be removed.
+
+### Main key holders
+
+All main key holders should revoke their signature(s) for the given key in a merge request to this repository using `keyringctl`.
+
+- [ ] @anthraxx
+- [ ] @artafinde
+- [ ] @demize
+- [ ] @dvzrv
+
+[no packages left in any of the official repositories]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/Find-packages-signed-by-a-key

.gitlab/merge_request_templates/New Main Key.md

+<!--
+This template is used when a new main PGP public key needs to be added to the distribution's keyring.
+It is used by users with a valid packager key after all steps in an accompanying issue (opened with the template "New Main Key") have been fulfilled.
+-->
+
+/label ~"new main key"
+/title Add main key of <!-- MODIFY: Add the main key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Add a new main key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the "long format" key ID of the PGP public key here -->
+
+Closes <!-- MODIFY: Add #-prefixed issue number, that will be closed by merging this merge request -->
+
+## Checks
+
+### Keyring maintainer
+
+- [ ] All steps in the accompanying ticket are fulfilled.
+
+### Main key holders
+
+- [ ] The public key has been validated according to the [best practices]
+
+[best practices](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair)

.gitlab/merge_request_templates/New Packager Key.md

+<!--
+This template is used when a new packager PGP public key needs to be added to the distribution's keyring.
+It is either used by the sponsor of a new packager or by an existing packager when adding a new key for themself after all steps in an accompanying issue (opened with the template "New Packager Key") have been fulfilled.
+-->
+
+/label ~"new packager key"
+/title Add packager key of <!-- MODIFY: Add the packager key holder's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Add a new packager key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the "long format" key ID of the PGP public key here -->
+
+Related issue: <!-- MODIFY: Add #-prefixed issue number -->
+
+## Checks
+
+- [ ] All steps in the accompanying ticket are fulfilled.
+
+### Main key holders
+
+- [ ] The public key has been validated according to the [best practices]
+
+[best practices]: https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair

.gitlab/merge_request_templates/Remove Main Key.md

+<!--
+This template is used when an existing main PGP public key needs to be removed from the distribution's keyring.
+It is used by users with a valid main key after all steps in an accompanying issue (opened with the template "Remove Main Key") have been fulfilled.
+-->
+/label ~"remove main key"
+/title Remove main key of <!-- MODIFY: Add the main key holder's username -->
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users. -->
+
+# Remove a main key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the "long format" key ID of the PGP public key here -->
+
+Related issue: <!-- MODIFY: Add #-prefixed issue number -->
+
+## Checks
+
+### Keyring maintainer
+
+- [ ] There are more than or equal to three valid main keys remaining after removal of this key.
+- [ ] All packagers have at least three valid main key signatures for their packager key after removal of this key.

.gitlab/merge_request_templates/Remove Packager Key.md

+<!--
+This template is used when an existing packager PGP public key needs to be removed from the distribution's keyring.
+It is used by users with a valid main key or a valid packager key after all steps in an accompanying issue (opened with the template "Remove Packager Key") have been fulfilled.
+-->
+
+/label ~"remove packager key"
+/title Remove packager key of <!-- MODIFY: Add the packager's username -->
+
+<!-- Please do not remove the above quick actions, which automatically label the issue and assign relevant users as reviewers. -->
+
+# Remove a packager key
+
+## Details
+
+- Username: <!-- MODIFY: Add the @-prefixed username -->
+- PGP key ID: <!-- MODIFY: Add the "long format" key ID of the PGP public key here -->
+
+Related issue: <!-- MODIFY: Add #-prefixed issue number -->
+
+## Checks
+
+### Keyring maintainer
+
+- [ ] There are no packages left in any of the official repositories, that are signed by the key which is about to be removed.

CONTRIBUTING.md

+# Contributing
+
+These are the contribution guidelines for archlinux-keyring.
+All code contributions fall under the terms of the GPL-3.0-or-later (see
+[LICENSE](LICENSE)).
+
+Please read our distribution-wide [Code of
+Conduct](https://terms.archlinux.org/docs/code-of-conduct/) before
+contributing, to understand what actions will and will not be tolerated.
+
+Development of archlinux-keyring takes place on Arch Linux' Gitlab:
+https://gitlab.archlinux.org/archlinux/archlinux-keyring.
+
+Any merge request to the repository requires two approvals of authorized
+approvers (the current main key holders).
+
+## Discussion
+
+Discussion around archlinux-keyring may take place on the [arch-projects
+mailing list](https://lists.archlinux.org/listinfo/arch-projects) and in
+[#archlinux-projects](ircs://irc.libera.chat/archlinux-projects) on [Libera
+Chat](https://libera.chat/).
+
+## Requirements
+
+The following additional packages need to be installed to be able to lint
+and develop this project:
+
+* python-black
+* python-coverage
+* python-isort
+* python-pytest
+* python-tomli
+* flake8
+* mypy
+
+## Keyringctl
+
+The `keyringctl` script is written in typed python, which makes use of
+[sequoia](https://sequoia-pgp.org/)'s `sq` command.
+
+The script is type checked, linted and formatted using standard tooling.
+When providing a merge request make sure to run `make lint`.
+
+## Testing
+
+Test cases are developed per module in the [test](test) directory and should
+consist of atomic single expectation tests. A Huge test case asserting various
+different expectations are discouraged and should be split into finer grained
+test cases.
+
+To execute all tests using pytest
+```bash
+make test
+```
+
+To run keyring integrity and consistency checks
+```bash
+make check
+```
+
+## Web Key Directory
+
+Only tagged releases are built and exposed via WKD. This helps to ensure, that
+inconsistent state of the keyring is not exposed to the enduser, which may make
+use of it instantaneously.

LICENSE

+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<https://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<https://www.gnu.org/licenses/why-not-lgpl.html>.

Makefile

-V=20200108
+SHELL = /bin/bash
+PREFIX ?= /usr/local
+BUILD_DIR ?= build
+KEYRING_TARGET_DIR ?= $(PREFIX)/share/pacman/keyrings/
+RELEASE ?=
+SCRIPT_TARGET_DIR ?= $(PREFIX)/bin
+SYSTEMD_SYSTEM_UNIT_DIR ?= $(shell pkgconf --variable systemd_system_unit_dir systemd)
+WKD_FQDN ?= archlinux.org
+WKD_BUILD_DIR ?= $(BUILD_DIR)/wkd/.well-known/
+KEYRING_FILE=archlinux.gpg
+KEYRING_REVOKED_FILE=archlinux-revoked
+KEYRING_TRUSTED_FILE=archlinux-trusted
+PROJECT=archlinux-keyring
+WKD_SYNC_SCRIPT=archlinux-keyring-wkd-sync
+WKD_SYNC_SERVICE_IN=archlinux-keyring-wkd-sync.service.in
+WKD_SYNC_SERVICE=archlinux-keyring-wkd-sync.service
+WKD_SYNC_TIMER=archlinux-keyring-wkd-sync.timer
+SYSTEMD_TIMER_DIR=$(SYSTEMD_SYSTEM_UNIT_DIR)/timers.target.wants/
+SOURCES := $(shell find keyring) $(shell find libkeyringctl -name '*.py' -or -type d) keyringctl
 
-PREFIX = /usr/local
+all: build
 
-install:
-	install -dm755 $(DESTDIR)$(PREFIX)/share/pacman/keyrings/
-	install -m0644 archlinux.gpg $(DESTDIR)$(PREFIX)/share/pacman/keyrings/
-	install -m0644 archlinux-trusted $(DESTDIR)$(PREFIX)/share/pacman/keyrings/
-	install -m0644 archlinux-revoked $(DESTDIR)$(PREFIX)/share/pacman/keyrings/
+lint:
+	black --check --diff keyringctl libkeyringctl tests
+	isort --diff .
+	flake8 keyringctl libkeyringctl tests
+	mypy --install-types --non-interactive keyringctl libkeyringctl tests
 
-uninstall:
-	rm -f $(DESTDIR)$(PREFIX)/share/pacman/keyrings/archlinux{.gpg,-trusted,-revoked}
-	rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(PREFIX)/share/pacman/keyrings/
+fmt:
+	black .
+	isort .
+
+check:
+	./keyringctl -v check
+
+test:
+	coverage run
+	coverage xml
+	coverage report --fail-under=100.0
+
+build: $(SOURCES)
+	./keyringctl -v build
+
+wkd: build
+	wkd-exporter --append --domain $(WKD_FQDN) $(WKD_BUILD_DIR) < $(BUILD_DIR)/$(KEYRING_FILE)
 
-dist:
-	git archive --format=tar --prefix=archlinux-keyring-$(V)/ $(V) | gzip -9 > archlinux-keyring-$(V).tar.gz
-	gpg --detach-sign --use-agent archlinux-keyring-$(V).tar.gz
+wkd_inspect: wkd
+	for file in $(WKD_BUILD_DIR)/openpgpkey/$(WKD_FQDN)/hu/*; do sq inspect --certifications $$file; done
 
-upload:
-	scp archlinux-keyring-$(V).tar.gz archlinux-keyring-$(V).tar.gz.sig repos.archlinux.org:/srv/ftp/other/archlinux-keyring/
+wkd_sync_service: wkd_sync/$(WKD_SYNC_SERVICE_IN)
+	sed -e 's|SCRIPT_TARGET_DIR|$(SCRIPT_TARGET_DIR)|' wkd_sync/$(WKD_SYNC_SERVICE_IN) > $(BUILD_DIR)/$(WKD_SYNC_SERVICE)
+
+clean:
+	rm -rf $(BUILD_DIR) $(WKD_BUILD_DIR)
+
+release: clean build
+	$(if $(RELEASE),,$(error RELEASE was not specified!))
+	@glab auth status -h gitlab.archlinux.org
+	@git tag -s $(RELEASE) -m "release version $(RELEASE)"
+	@git push origin refs/tags/$(RELEASE)
+	@mkdir -p $(BUILD_DIR)/$(PROJECT)-$(RELEASE)/
+	@cp $(BUILD_DIR)/{$(KEYRING_FILE),$(KEYRING_REVOKED_FILE),$(KEYRING_TRUSTED_FILE)} $(BUILD_DIR)/$(PROJECT)-$(RELEASE)/
+	@tar cvfz $(BUILD_DIR)/$(PROJECT)-$(RELEASE).tar.gz -C $(BUILD_DIR)/ $(PROJECT)-$(RELEASE)/
+	@gpg -o $(BUILD_DIR)/$(PROJECT)-$(RELEASE).tar.gz.sig --default-key "$(shell git config --local --get user.signingkey)" -s $(BUILD_DIR)/$(PROJECT)-$(RELEASE).tar.gz
+	# NOTE: we specify GITLAB_HOST, because otherwise glab YOLO uses whatever is specified by the `host` key in its config and silently breaks all links...
+	GITLAB_HOST=gitlab.archlinux.org glab release create $(RELEASE) ./build/$(PROJECT)-$(RELEASE).tar.gz* --name=$(RELEASE) --notes="release version $(RELEASE)"
+
+install: build wkd_sync_service
+	install -vDm 644 build/{$(KEYRING_FILE),$(KEYRING_REVOKED_FILE),$(KEYRING_TRUSTED_FILE)} -t $(DESTDIR)$(KEYRING_TARGET_DIR)
+	install -vDm 755 wkd_sync/$(WKD_SYNC_SCRIPT) -t $(DESTDIR)$(SCRIPT_TARGET_DIR)
+	install -vDm 644 build/$(WKD_SYNC_SERVICE) -t $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR)
+	install -vDm 644 wkd_sync/$(WKD_SYNC_TIMER) -t $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR)
+	install -vdm 755 $(DESTDIR)$(SYSTEMD_TIMER_DIR)
+	ln -fsv ../$(WKD_SYNC_TIMER) $(DESTDIR)$(SYSTEMD_TIMER_DIR)/$(WKD_SYNC_TIMER)
+
+uninstall:
+	rm -fv $(DESTDIR)$(KEYRING_TARGET_DIR)/{$(KEYRING_FILE),$(KEYRING_REVOKED_FILE),$(KEYRING_TRUSTED_FILE)}
+	rmdir -pv --ignore-fail-on-non-empty $(DESTDIR)$(KEYRING_TARGET_DIR)
+	rm -v $(DESTDIR)$(SCRIPT_TARGET_DIR)/$(WKD_SYNC_SCRIPT)
+	rmdir -pv --ignore-fail-on-non-empty $(DESTDIR)$(SCRIPT_TARGET_DIR)
+	rm -v $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR)/{$(WKD_SYNC_SERVICE),$(WKD_SYNC_TIMER)}
+	rmdir -pv --ignore-fail-on-non-empty $(DESTDIR)$(SYSTEMD_SYSTEM_UNIT_DIR)
+	rm -v $(DESTDIR)$(SYSTEMD_TIMER_DIR)/$(WKD_SYNC_TIMER)
+	rmdir -pv --ignore-fail-on-non-empty $(DESTDIR)$(SYSTEMD_TIMER_DIR)
 
-.PHONY: install uninstall dist upload
+.PHONY: all build lint fmt check test clean install release uninstall wkd wkd_inspect

README.md

-# Arch Linux Keyring
+# archlinux-keyring
 
-Repository for the Arch Linux keyring package.
+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.
 
-## Addition/Removal/Update of a packaging key
+The PGP packets describing the main signing keys can be found below the
+[keyring/main](keyring/main) directory, while those of the packagers are located below the
+[keyring/packager](keyring/packager) directory.
 
-1. Get the keyid from the bugreport in the [keyring
-   project](https://bugs.archlinux.org/index.php?project=7&do=index&switch=1)
-2. Add the keyid to `packager-keyids` in alphabetic order, following this
-   format: full size keyid, a tab, nickname.
+## Requirements
 
-## Revoking a packager key
+The following packages need to be installed to be able to create a PGP keyring
+from the provided data structure and to install it:
 
-1. Create a key removal task in the [keyring
-   project](https://bugs.archlinux.org/index.php?project=7&do=index&switch=1).
-2. Remove the keyid of the revoked user from `packager-keyids`.
-3. Add the removed keyid to `packager-revoked-keyids`, in alphabetic order,
-   following this format: full size keyid, a tab, nickname, a tab and reason of
-   revocation.
+Build:
 
-## Keyring release
+* make
+* findutils
+* pkgconf
+* systemd
 
-1. bump the version in the Makefile
-2. Run update-keys
-4. git add the new .asc file in the packager directory.
-4. Commit everything as 'Update keyring'
-5. Create a new tag ```git tag -s $(date +"%Y%m%d")```
-6. Push changes
-7. Upload the source tarball with ```make dist upload```
-8. Update the package
+Runtime:
+
+* python
+* sequoia-sq >= 0.31.0
+
+Optional:
+
+* hopenpgp-tools (verify)
+* git (ci)
+
+## Usage
+
+### Build
+
+Build all PGP artifacts (keyring, ownertrust, revoked files) to the build directory
+```bash
+./keyringctl build
+```
+
+### Import
+
+Import a new packager key by deriving the username from the filename.
+```bash
+./keyringctl import <username>.asc
+```
+
+Alternatively import a file or directory and override the username
+```bash
+./keyringctl import --name <username> <file_or_directory...>
+```
+
+Updates to existing keys will automatically derive the username from the known fingerprint.
+```bash
+./keyringctl import <file_or_directory...>
+```
+
+Main key imports support the same options plus a mandatory `--main`
+```bash
+./keyringctl import --main <username>.asc
+```
+
+### Export
+
+Export the whole keyring including main and packager to stdout
+```bash
+./keyringctl export
+```
+
+Limit to specific certs using an output file
+```bash
+./keyringctl export <username_or_fingerprint_or_directory...> --output <filename>
+```
+
+### List
+
+List all certificates in the keyring
+```bash
+./keyringctl list
+```
+
+Only show a specific main key
+```bash
+./keyringctl list --main <username_or_fingerprint...>
+```
+
+### Inspect
+
+Inspect all certificates in the keyring
+```bash
+./keyringctl inspect
+```
+
+Only inspect a specific main key
+```bash
+./keyringctl inspect --main <username_or_fingerprint_or_directory...>
+```
+
+### Verify
+
+Verify certificates against modern expectations and assumptions
+```bash
+./keyringctl verify <username_or_fingerprint_or_directory...>
+```
+
+## Installation
+
+To install archlinux-keyring system-wide use the included `Makefile`:
+
+```bash
+make install
+```
+
+## Contribute
+
+Read our [contributing guide](CONTRIBUTING.md) to learn more about guidelines and
+how to provide fixes or improvements for the code base.
+
+## Releases
+
+[Releases of
+archlinux-keyring](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/tags)
+are exclusively created by [keyring maintainers](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/project_members?with_inherited_permissions=exclude).
+
+The tags are signed with one of the following legitimate keys:
+
+```
+Christian Hesse <eworm@archlinux.org>
+02FD 1C7A 934E 6145 4584  9F19 A623 4074 498E 9CEE
+
+David Runge <dvzrv@archlinux.org>
+991F 6E3F 0765 CF62 9588  8586 139B 09DA 5BF0 D338
+
+Johannes Löthberg <demize@archlinux.org>
+5134 EF9E AF65 F95B 6BB1  608E 50FB 9B27 3A9D 0BB5
+
+Leonidas Spyropoulos <artafinde@archlinux.org>
+B4B7 5962 5D46 3343 0B74  8770 59E4 3E10 6B24 7368
+
+Levente Polyak <anthraxx@archlinux.org>
+E240 B57E 2C46 30BA 768E  2F26 FC1B 547C 8D81 72C8
+
+Morten Linderud <foxboron@archlinux.org>
+C100 3466 7663 4E80 C940  FB9E 9C02 FF41 9FEC BE16
+```
+
+To verify a tag, first import the relevant PGP keys:
+
+```bash
+gpg --auto-key-locate wkd --search-keys <email-from-above>
+```
+
+Afterwards a tag can be verified from a clone of this repository. Please note
+that one **must** check the used key of the signature against the legitimate
+keys listed above:
+
+```bash
+git verify-tag <tag>
+```
+
+## License
+
+Archlinux-keyring is licensed under the terms of the **GPL-3.0-or-later** (see
+[LICENSE](LICENSE)).

archlinux-revoked

-27FFC4769E19F096D41D9265A04F9397CDFD6BB0
-44D4A033AC140143927397D47EFD567D4C7EA887
-684148BB25B49E986A4944C55184252D824B18E8
-50F33E2E5B0C3D900424ABE89BDCF497A4BBCC7F
-4FCF887689C41B09506BE8D5F3E1D5C5D30DB0AD
-40776A5221EF5AD468A4906D42A1DB15EC133BAD
-5A2257D19FF7E1E0E415968CE62F853100F0D0F0
-66BD74A036D522F51DD70A3C7F2A16726521E06D
-9515D8A8EAB88E49BB65EDBCE6B456CAF15447D5
-BC1FBE4D2826A0B51E47ED62E2539214C6C11350
-E7210A59715F6940CF9A4E36A001876699AD6E84
-5696C003B0854206450C8E5BE613C09CB4440678
-40440DC037C05620984379A6761FAD69BA06C6A9
-63F395DE2D6398BBE458F281F2DBB4931985A992
-5559BC1A32B8F76B3FCCD9555FA5E5544F010D48
-5357F3B111688D88C1D88119FCF2CB179205AC90
-07DFD3A0BC213FA12EDC217559B3122E2FA915EC
-5E7585ADFF106BFFBBA319DC654B877A0864983E
-4D913AECD81726D9A6C74F0ADA6426DD215B37AD
-F5A361A3A13554B85E57DDDAAF7EF7873CFD4BB6
-8F76BEEA0289F9E1D3E229C05F946DED983D4366
-7FA647CD89891DEDC060287BB9113D1ED21E1A55
-D4DE5ABDE2A7287644EAC7E36D1A9E70E19DAA50
-81D7F8241DB38BC759C80FCE3A726C6170E80477
-D921CABED130A5690EF1896E81AF739EC0711BF1
-8840BD07FC24CB7CE394A07CCF7037A4F27FB7DA
-76B4192E902C0A52642C63C273B8ED52F1D357C1
-0B20CA1931F5DA3A70D0F8D2EA6836E1AB441196
-34C5D94FE7E7913E86DC427E7FB1A3800C84C0A5
-65EEFE022108E2B708CBFCF7F9E712E59AF5F22A
-FB871F0131FEA4FB5A9192B4C8880A6406361833
-8CF934E339CAD8ABF342E822E711306E3C4F88BC
-39F880E50E49A4D11341E8F939E4F17F295AFBF4
-B1F2C889CB2CCB2ADA36D963097D629E437520BD
-4A8B17E20B88ACA61860009B5CED81B7C2E5C0D2

archlinux-trusted

-AB19265E5D7D20687D303246BA1DFB64FFF979E7:4:
-D8AFDDA07A5B6EDFA7D8CCDAD6D055F927843F1C:4:
-DDB867B92AA789C165EEFA799B729B06A680C281:4:
-91FFE0700E80619CEB73235CA88E23E377514E00:4:
-0E8B644079F599DFC1DDC3973348882F6AC6A4C2:4: