Page MenuHome GnuPG

Keyserver access on Windows broken (Resource Temporary Unavailable)
Closed, ResolvedPublic


Reported in IRC and in wald:

I can reproduce the error. Next step for me is to run a git bisect.

Event Timeline

aheinecke lowered the priority of this task from Unbreak Now! to Needs Triage.Jul 31 2017, 8:41 AM

Uhm. I can't reproduce this with a dirmngr built on my development system.

aheinecke triaged this task as High priority.

It's either rev: 5b9025cfa1f9b1c67ddf2f6bf87d863e780cf157 which does not compile by itself or 3419a339d9c4e800bf30e9021e05982d8c1021c1

Last good revision: e051e396156211449568afa0ca7505dc13eaa3b4

First bad revision that compiles: 3419a339d9c4e800bf30e9021e05982d8c1021c1

Sorry. Git log had some ...skipping which i overlooked instead of 3419a339d9c4e800bf30e9021e05982d8c1021c1 the actual one is 9b43220b8ad1a5c1cd51de3bbfff7ccbcc3fa877

Workaround is to add

connect-timeout 0
connect-quick-timeout 0

to dirmngr.conf and

gpgconf --reload dirmnrg

How, shall we build just a new patched installer or do a full new release?

I'd say a patched installer with a different date. This is how I would have handled this in the Gpg4win 2.x times.

Or you publish some gnupg-2.1.23-beta3 or so. Would also be ok imo.

Patched installer is better. This is also a good test on whether the build works with custom patches.