On 10/06/2015 10:23 AM, Yuri Kanivetsky wrote: > Hi, > ..
> > Do you have any clues? Is there anything I can check? I'm not using > proxy, if anything. > > Regards, Yuri It would be helpful to have information regarding which version of gnupg this is using, and if <2.1 how the keyserver helpers were built, primarily whether using full curl implementation or curl-shim. This can be checked using $ gpg --keyserver-options verbose,debug --keyserver hkp://keys.gnupg.net --recv-key 0x409B6B1796C275462A1703113804BB82D39DC0E3 and one one of my VMs still running 2.0 reports gpg: requesting key D39DC0E3 from hkp server keys.gnupg.net gpgkeys: curl version = libcurl/7.43.0 OpenSSL/1.0.2d zlib/1.2.8 Output from "dig" or similar tools as to the state of the DNS resolver likely used is also helpful. Another potential issue that comes up from time to time is IPv4 vs IPv6, so pay attention to the address it is trying to connect to in the output. -- ---------------------------- Kristian Fiskerstrand Blog: http://blog.sumptuouscapital.com Twitter: @krifisk ---------------------------- Public OpenPGP key 0xE3EDFAE3 at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 ---------------------------- "The power of accurate observation is commonly called cynicism by those who have not got it." George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
