Regarding /edit: (2026-05-07), this key did not refresh for me:
gpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16
gpg: refreshing 1 key from hkps://keyserver.ubuntu.com
gpg: keyserver refresh failed: Try again later'
The problem is that dirmngr work properly in certain builds due to a known incompatibility between dirmngr's ADNS resolver and systemd-resolved's stub listener. The standard-resolver directive in dirmngr.conf should fix that, but it didn't.
This resolved the issue:
curl -sL "https://keys.openpgp.org/vks/v1/by-fingerprint/662E3CDD6FE329002D0CA5BB40339DD82B12EF16" -o /tmp/lw.pgp
file /tmp/lw.pgp
gpg --import /tmp/lw.pgp
/tmp/lw.pgp: PGP public key block
Pinned Comments
lsf commented on 2021-11-10 12:14 (UTC) (edited on 2026-05-07 09:38 (UTC) by lsf)
https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)/edit: (2026-05-07): The upstream signing sub-key was rotated, and the
.tar.xztarballs will now be signed with a new subkey. The main key id (0x662E3CDD6FE329002D0CA5BB40339DD82B12EF16) remains unchanged though, so should you get an error during signature verification about a missing (sub)key, all that's required would be to refresh the key(s) viagpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.