Revisions and Commits
|rG15d2a009931f dirmngr: Implement querying nameservers over IPv6.|
dirmngr[9.5]: handler for fd 5 started dirmngr[9.5]: connection from process 10 (1000:1000) dirmngr[9.5]: command 'KS_GET' failed: Server indicated a failure <Unspecified source> gpg: keyserver receive failed: Server indicated a failure dirmngr[9.5]: handler for fd 5 terminated
debian stretch's 2.1.18 also suffers from this (debian bug tracker). As there is only 13 days left for fixing issues in stretch, swift action is needed.
as using sthe standard-resolver solves this, is there an issue using that by default? Which resolver does it actually use, and anyway, why does gnupg not use the standard resolver by default?
in particular, do you see issues with placing
Dirmngr uses its own resolver for these reasons:
- custom timeout handling.
- forcing use of TCP so to be able to go via Tor.
- common code on all platforms; in particular we can use that resolver also on Windows.