No connection to Keyserver possible
Open, NormalPublic

Description

Hi @ all,

in our company we are using an sks to store GnuPG Keys of our coustomers to use them for secure file transfers. This sks was running pretty well with Kleopatra Version 2.2.0-gitac229d2 (2014-08-11).

After an update to Version 3.1.3-gpg4win-3.1.4 the URL/IP of the sks is still present in settings (Format: hkp://NNN.NNN.NNN.NNN without portnumber)
but i am not able to establish a connection to the sks. Every search is unsuccessful.
Also it is no longer possible to publish a new key to the server.

From other machines still running Version 2.2.0-gitac229d2 (2014-08-11) everything is fine so i asume that there is a problem with the actual version.

cheers

Michel

Details

Version
3.1.3-gpg4win-3.1.4
Michel created this task.Nov 9 2018, 2:22 PM
aheinecke triaged this task as Normal priority.Nov 10 2018, 3:48 PM
aheinecke added a subscriber: aheinecke.

Strange, I don't know of an issue that is related to that. There were a lot of changes to the DNS code but if you are using an IP. I've tested that using an IP works for me. I used https://192.146.137.99:443 for testing.

could you please try on the command line (cmd.exe)

gpg --search someaddress

And note the error here?

Thanks for reply.

I tried to search the keyserver from comand line. gpg --search <exact mailadress> results in follwing message:

gpg: Kein Schlüsselserver bekannt (Option --keyserver verwenden)
gpg: Suche auf dem Schlüsselserver fehlgeschlagen: Kein Schlüsselserver verfügbar

In Kleopatra settings there is still the IP from my keyserver present (see attached image). The sks webinterface is accessible from my machine and a search for the same term delivers the correct results.

aheinecke assigned this task to werner.
aheinecke added a subscriber: werner.

I can reproduce it if I enter your or an unknown IP address.

I think the problem is that dirmngr tries a reverse dns search for the IP:

2018-11-12 10:19:09 dirmngr[39496.10] resolve_dns_addr for '192.146.137.99': 'pgpkeys.co.uk' [already known]

Your server is of course unreachable to me. But I find the Line

2018-11-12 10:15:54 dirmngr[39496.6] can't connect to '172.29.210.4': no IP address for host

In my log interesting. No IP address for an IP address? :-)

2018-11-12 10:15:54 dirmngr[39496.6] resolve_dns_addr failed while checking '172.29.210.4': No name
2018-11-12 10:15:54 dirmngr[39496.6] can't connect to '172.29.210.4': no IP address for host
2018-11-12 10:15:54 dirmngr[39496.6] error connecting to 'http://172.29.210.4:11371': Unknown host
2018-11-12 10:15:54 dirmngr[39496.6] marking host '172.29.210.4' as dead
2018-11-12 10:15:54 dirmngr[39496.6] host '172.29.210.4' marked as dead
2018-11-12 10:15:54 dirmngr[39496.6] command 'KS_SEARCH' failed: No keyserver available

@werner ^ this is not a Windows specific thing and I don't know the dns code well.