On Mon Dec 1, 2025 at 11:19 PM CET, Genes Lists wrote: > Note also that gpg relies on gnutls and gnutls has had TLS protocol > bugs in the past (e.g. [1] which was fixed earlier this year). > > So it may be helpful to try both gnupg and sequoia to see if they both > have a problem. If one works and one fails, it suggests a client side > problem. Running these directly may also provide more info about the > source of any failure. > > For example, both of these examples work fine for me. They check the > first username in the list of failures you provided. > > using gpg: > > gpg -v --auto-key-locate clear,wkd,nodefault \ > --locate-external-keys [email protected] > > and using sequoia > > sq network wkd search [email protected] > > > > [1] https://gitlab.com/gnutls/gnutls/-/issues/1660 > > gene
Both work, which means that my IP range is probably being rate-limited somehow when using the service due to the amount of keys it accesses while running. -- Ariadna Vigo https://ariadnavigo.xyz gpg 0xC948873069856D6D
signature.asc
Description: PGP signature
