-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I am running GnuPG 2.1.2 on Windows 10, using the pre-compiled
binaries. Keyserver lookup keeps failing for me as follows:-
>gpg -v --keyserver hkp://pool.sks-keyservers.net --recv-key 0x251BCCEB547B7194
gpg: using character set 'utf-8'
gpg: keyserver receive failed: No keyserver available
>gpg-connect-agent --dirmngr "keyserver --hosttable" /bye
S # hosttable (idx, ipv6, ipv4, dead, name, time):
S # 0 d pool.sks-keyservers.net (14m50s)
OK
I tried pinging pool.sks-keyservers.net:-
>ping -6 pool.sks-keyservers.net
Pinging pool.sks-keyservers.net [2001:67c:2e80:40:21e:67ff:fe14:69f4] with 32
bytes of data:
Reply from 2001:67c:2e80:40:21e:67ff:fe14:69f4: time=22ms
Reply from 2001:67c:2e80:40:21e:67ff:fe14:69f4: time=21ms
Reply from 2001:67c:2e80:40:21e:67ff:fe14:69f4: time=22ms
Reply from 2001:67c:2e80:40:21e:67ff:fe14:69f4: time=21ms
Ping statistics for 2001:67c:2e80:40:21e:67ff:fe14:69f4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 21ms
>ping -4 pool.sks-keyservers.net
Pinging pool.sks-keyservers.net [176.241.243.15] with 32 bytes of data:
Reply from 176.241.243.15: bytes=32 time=45ms TTL=50
Reply from 176.241.243.15: bytes=32 time=45ms TTL=50
Reply from 176.241.243.15: bytes=32 time=44ms TTL=50
Reply from 176.241.243.15: bytes=32 time=44ms TTL=50
Ping statistics for 176.241.243.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 45ms, Average = 44ms
Any ideas how to proceed?
- --
Best regards
MFPA <mailto:2014-667rhzu3dc-lists-gro...@riseup.net>
Alcohol and Calculus don't mix. Never drink and derive.
-----BEGIN PGP SIGNATURE-----
iQF8BAEBCgBmBQJXTsleXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCM0FFN0VDQTlBOEM4QjMwMjZBNUEwRjU2
QjdDNzRDRUIzMUYyNUYwAAoJEGt8dM6zHyXwDewIAK9G+bxZL+dUu7fXJN0rih9d
7EISoZgrZ/ybxMPFciOXgHvC476EtZR4DYqowy+Z9bUtNTSGwZ5/LkmzSVm/TG3H
gPiRRVloMJWAzCDPLPxRoi0xJ4tPpKt0xr9X8zqhuhMoYVsZkbMLz0/C8fp1/v+r
jrd8G7lbmalL5yK7lw5y6Ioc7XY+kZJElbY0xW9Cs7OL6m4lJCMDn5PNhZMALWpi
LyZPijBfSwl/YpCf8HhlnmzXzWdDzNT83j9EHQEkh/IwhjmbGpmTJG+QL++xR+KS
N6RLwg9akJNk9LHTfznvamLVGQs32ZDTi5SgHNRVonc5Ziz1ivqQi7E8lRC2OhSI
vgQBFgoAZgUCV07JbF8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu
cGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNBQ0VENEVFOTEzNEVFQkRFNkE4NTA2MTcx
MkJDNDYxQUY3NzhFNAAKCRAXErxGGvd45D5WAP42dMUW3jvaYAJaA7Zxy2m4j3yc
I1ndF3yQG8JMBN9+QAD/bOyVITPDGA7tpC6NjSUaLLCsvJ78i4L9DYnJil85RgQ=
=pZ5i
-----END PGP SIGNATURE-----
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
