Remove packager key of sudoforge
Remove a packager key
Details
- Username: @sudoforge
- PGP key ID: FAD824618B562B99CCCE05FB905A8C3700E16349
- Resignation: https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/thread/7URXW2HJESG42C5M4J2UG6YUEVF6K4KH/
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
.
- Show closed items
Related merge requests 1
When this merge request is accepted, this issue will be closed automatically.
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- Evangelos Foutras added remove packager key label
added remove packager key label
- Evangelos Foutras marked the checklist item There are [no packages left in any of the official as completed
marked the checklist item There are [no packages left in any of the official as completed
- Developer
The key doesn't have any signatures from main key holders.
Collapse replies - Author Reporter
Doesn't the key still need to be removed from the keyring?
- Developer
Hm, I don't think so. It will eventually expire:
./keyringctl inspect sudoforge WARNING: sq does not have a stable CLI interface. Use with caution in scripts. /run/user/1000/arch-keyringctl-gf15l35a/packet-lb5ongrx.asc: OpenPGP Certificate. Fingerprint: FAD824618B562B99CCCE05FB905A8C3700E16349 sudoforge ~ unknown Public-key algo: EdDSA Public-key size: 256 bits Creation time: 2022-06-09 14:21:11 UTC Expiration time: 2025-01-31 11:54:07 UTC (creation time + P966DT77576S) Key flags: certification Subkey: 247C5662524E6EFCF4000027DC32C13A989E0DA2 Public-key algo: EdDSA Public-key size: 256 bits Creation time: 2022-06-09 14:37:07 UTC Expiration time: 2025-01-31 11:54:17 UTC (creation time + P966DT76630S) Key flags: authentication Subkey: 6F1794FBCF261ECC05B7F5AD877F9F855FF542E9 Public-key algo: EdDSA Public-key size: 256 bits Creation time: 2022-06-09 14:36:07 UTC Expiration time: 2025-01-31 11:54:17 UTC (creation time + P966DT76690S) Key flags: signing Subkey: BEED5A2156B1F10FC63C251668A16F68D747E833 Public-key algo: ECDH Public-key size: 256 bits Creation time: 2022-06-09 14:36:41 UTC Expiration time: 2025-01-31 11:54:17 UTC (creation time + P966DT76656S) Key flags: transport encryption, data-at-rest encryption UserID: sudoforge <sudoforge@archlinux.org>
As it is already part of user's pacman keyring, removing it here would unfortunately not have much of an effect.
If @sudoforge was to revoke the key and add the revocation certificate, that would help though!
1 - Author Reporter
I still think it's worthwhile to revert 10bbb50a. As you say, it doesn't help with existing pacman keyrings, but for new and even re-populated ones, it does make for a cleaner state.
- Developer
I guess the revocation would even be better then. It's just questionable when this will happen
1 - Contributor
i'm currently traveling (and will be for the next ~4 months), without access to the revocation certificate for this key (it's in a secure place back in my home country).
unfortunate timing here. wouldn't we be able to remove it from users' keyrings via the
*.install
script? - Developer
From my perspective there is no immanent hurry. If you could revoke it (and add that updated cert to this repository) once you're home, that'd be ace!
- Contributor
yeah, that won't be a problem once i'm back. just to provide as accurate a timeline as i can, i'm gone until at least the end of may 2023, and at most through the end of july 2023.
- Developer
@sudoforge just a quick ping checking whether you are back already
- Developer
@sudoforge Hi! we have entered August now. Can you please revoke your key?
- Developer
@sudoforge as announced in your private mail to me you should now have access to your key material again. Can you please revoke your key?
- Developer
Sent yet another reminder email.
- Developer
Sent yet another reminder email...
- David Runge closed
closed
- David Runge reopened
reopened
- David Runge unassigned @pierre
unassigned @pierre
- David Runge marked the checklist item @anthraxx as completed
marked the checklist item @anthraxx as completed
- David Runge marked the checklist item @demize as completed
marked the checklist item @demize as completed
- David Runge marked the checklist item @bluewind as completed
marked the checklist item @bluewind as completed
- David Runge marked the checklist item @diabonas as completed
marked the checklist item @diabonas as completed
- David Runge marked the checklist item @dvzrv as completed
marked the checklist item @dvzrv as completed
- David Runge marked the checklist item @pierre as completed
marked the checklist item @pierre as completed
- Developer
@sudoforge please revoke this key, so that it is properly marked on existing and new installations.
- David Runge unassigned @diabonas
unassigned @diabonas
- David Runge mentioned in commit 4c0c7a60
mentioned in commit 4c0c7a60
- David Runge mentioned in merge request !331 (merged)
mentioned in merge request !331 (merged)
- David Runge closed with merge request !331 (merged)
closed with merge request !331 (merged)
- David Runge closed with commit 4c0c7a60
closed with commit 4c0c7a60