Re: Refreshing keyring via WKD
Ingo Klöcker <[email protected]> Mon, 23 Mar 2026 09:03:10 +0100
| Newsgroups | gmane.comp.encryption.gpg.user |
|---|---|
| Message-ID | <4869799.vXUDI8C0e8@daneel> |
On Sonntag, 22. März 2026 20:21:18 Mitteleuropäische Normalzeit Ingo Klöcker wrote: > On Sonntag, 22. März 2026 18:31:30 Mitteleuropäische Normalzeit Werner Koch > > via Gnupg-users wrote: > > On Sun, 22 Mar 2026 13:29, Seth McDonald said: > > > To my understanding, GnuPG has been encouraging the use of WKD over > > > keyservers for the distribution of public keys. I personally use WKD as > > > > Right, except for organizational-wide LDAP keyservers. > > > > > Though when it comes to updating my keyring via --refresh-keys, GnuPG > > > seems to only be able to use keyservers to obtain the up-to-date keys. > > > > Yes, this is an open task. > > Kleopatra already can update multiple keys in one go. Simply select the > OpenPGP certificates you want to update and then select "Update > Certificates". Kleopatra queries WKD and the configured OpenPGP keyserver. > If you just want to update via WKD then temporarily remove the configured > keyserver. I forgot that one has to enable the option "Query certificate directories of providers for all user IDs" if all keys should be updated via WKD. Otherwise, only keys that were originally retrieved via WKD are updated via WKD. Regards, Ingo _______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
signature.asc
(application/pgp-signature, 265 B)
-----BEGIN PGP SIGNATURE----- iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCacDzvhsUgAAAAAAEAA5t YW51MiwyLjUrMS4xMiwyLDIACgkQsW9ZlRZHSrq1tgEA5PKC1F7oAmWRf10fFqRU JDxR+rTVo+qmNOclSOIS6h4BAJJE37137dHGh3gQfVp6C5kXWC+iwzQwZ+bKx5Oe JDMC =POBO -----END PGP SIGNATURE-----