... | ... | @@ -49,10 +49,11 @@ |
|
|
- Wait for the revocation certificate holder to verify, that the revocation certificate works
|
|
|
7. Upload public key to keyserver infrastructure
|
|
|
- `gpg --keyserver keyserver.ubuntu.com --send-key <key ID>`
|
|
|
8. Add the public key to the distribution keyring
|
|
|
- Open an issue in the [archlinux-keyring](https://gitlab.archlinux.org/archlinux/archlinux-keyring) repository using the "New Main Key" template
|
|
|
- Create a merge request to add the new key ID to [master-keyids](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/blob/master/master-keyids)
|
|
|
- Release new version of the keyring
|
|
|
8. Add the public key to [archlinux-keyring](https://gitlab.archlinux.org/archlinux/archlinux-keyring):
|
|
|
- [Open an issue](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/issues/new) using the "New Main Key" template
|
|
|
- Import the public key as a new main key: `./keyringctl import --main --name <username> <(gpg --export <key ID>)`
|
|
|
- [Create a merge request](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/merge_requests/new) to add the PGP packets in the keyring directory
|
|
|
- Release new version of archlinux-keyring
|
|
|
9. Publish public key via WKD
|
|
|
- Trigger a new deployment of the public keys via [WKD](https://gitlab.archlinux.org/archlinux/wkd/)
|
|
|
10. Publish the new key on the website
|
... | ... | |