Dirmngr fails to communicate with keyservers (W32 binaries for GnuPG 2.1.22)

MFPA 2014-667rhzu3dc-lists-groups at riseup.net
Sat Jul 29 15:58:09 CEST 2017


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


I have installed the W32 package for GnuPG 2.1.22 and I find keys
cannot be sent to keyservers, or fetched/refreshed. The operation
fails with the message "keyserver send failed: Resource temporarily
unavailable".

In the event the dirmngr from 2.1.21 is already running, the operation
succeeds.



[path_to]\GnuPG_2_1_22\bin>gpg --send-key 0xF5AECE1EF251BFAB
gpg: using character set 'utf-8'
gpg: no running Dirmngr - starting
'[path_to]\GnuPG_2_1_22\bin\dirmngr.exe'

gpg: waiting for the dirmngr to come up ... (5s)
gpg: waiting for the dirmngr to come up ... (4s)
gpg: connection to the dirmngr established
gpg: Invalid key 0xF5AECE1EF251BFAB made valid by
- --allow-non-selfsigned-uid

gpg: sending key 0xF5AECE1EF251BFAB to hkp://pool.sks-keyservers.net
gpg: Note: signature key 0xF5AECE1EF251BFAB has been revoked
gpg: Note: signature key 0xF5AECE1EF251BFAB has been revoked
gpg: keyserver send failed: Resource temporarily unavailable
gpg: keyserver send failed: Resource temporarily unavailable





Compare with:

[path_to]\GnuPG_2_1_22\bin>gpg --send-key 0xF5AECE1EF251BFAB
gpg: using character set 'utf-8'
gpg: WARNING: server 'dirmngr' is older than us (2.1.21 < 2.1.22)
gpg: Invalid key 0xF5AECE1EF251BFAB made valid by
- --allow-non-selfsigned-uid

gpg: sending key 0xF5AECE1EF251BFAB to hkp://pool.sks-keyservers.net
gpg: Note: signature key 0xF5AECE1EF251BFAB has been revoked
gpg: Note: signature key 0xF5AECE1EF251BFAB has been revoked




- --
Best regards

MFPA                  <mailto:2014-667rhzu3dc-lists-groups at riseup.net>

It's not hard to meet expenses, they're everywhere.
-----BEGIN PGP SIGNATURE-----

iNUEARYKAH0WIQQzrO1O6RNO695qhQYXErxGGvd45AUCWXyUeV8UgAAAAAAuAChp
c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNB
Q0VENEVFOTEzNEVFQkRFNkE4NTA2MTcxMkJDNDYxQUY3NzhFNAAKCRAXErxGGvd4
5MMNAQC4QqhxRYa/L8rMfoyfcYDixQOr6uskMoN/bDwdBmPCwwEAtlNVH+dlE5h/
xLesXjjiB8+rU1KK+mSJnhGgFPEFVAqJAZMEAQEKAH0WIQSzrn7KmoyLMCaloPVr
fHTOsx8l8AUCWXyUkV8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0QjNBRTdFQ0E5QThDOEIzMDI2QTVBMEY1NkI3
Qzc0Q0VCMzFGMjVGMAAKCRBrfHTOsx8l8FC0CADAWYNuxXCeEdVIc1L8HC6WZHG/
oUYEyGnPIgFfczjzLgU+fHbpJnzk4PdJZVEhlTqYb3rg+5Wr55UcTStskbmP6tcR
xBBKx+8hk7s9pIH4iCZgbN9DF9oT9ENdFV/ODSBgpI8IVDiE+02DHXaZLQCTjIP2
YOvInshDJheKAq+ZnL4T9BBma3NCvvzoCD61Z+35VuUcxSq8uCjw6vEnMAHGoCdG
sCCSa6X0Ch+becbsWJmkeSoOL7eDE/TVuLBpy85F+O3xlRrcqGxzERAqsXKP34t/
OVt2Q+HUFVfObPnHxG4DUk3nYA3ja+yS1QvwD8z3Bz/WnYb4hGJpikBKuXkT
=yPGQ
-----END PGP SIGNATURE-----




More information about the Gnupg-users mailing list