Re: Keyserver lookup failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thursday 2 June 2016 at 3:43:10 AM, in , MFPA wrote: > Thanks for replying. Port 11371 is not blocked:- [snipped] Sorry. I just spotted the reason in "[Announce] GnuPG 2.1.12 released":- "This Windows installer comes with [...]

Re: Keyserver lookup failure

Hi On Wednesday 1 June 2016 at 5:31:30 PM, in , Kristian Fiskerstrand wrote: > what is the dig +trace output and any firewall > blocking port 11371 anywhere? Thanks for replying. Port 11371 is not blocked:- I can reach a keyserver's web interface in my browser at

Re: Keyserver lookup failure

On 06/01/2016 01:39 PM, MFPA wrote: > > 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: k

Re: Keyserver lookup failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wednesday 1 June 2016 at 1:34:15 PM, in , Brian Minton wrote: > That was a known bug in that version. > Try the most recent release, 2.1.12. Oops. That was a typo; I am using version 2.1.12. - -- Best regards MFPA

Re: Keyserver lookup failure

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 That was a known bug in that version. Try the most recent release, 2.1.12. -BEGIN PGP SIGNATURE- iIAEAREKACghHEJyaWFuIE1pbnRvbiA8YnJpYW5AbWludG9uLm5hbWU+BQJXTtYM AAoJEGuOs6Blz7qpUSEA/1eOzIohTnrAEA2RMIWbRpjeqYAuuoptzBK9zT2D8kNC AP9WO0ubiiHcMX

Keyserver lookup failure

-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: keyser

Re: Keyserver lookup failure, redux

> I can confirm that the exact above command works for me (on OS X), with > gpg 2.1.8: How odd. All right -- time for me to assume there's some problem with how OS X has borked IPv6 configuration. (I don't even have IPv6 connectivity; why OS X insists on giving me IPv6 addresses, I don't know.)

Re: Keyserver lookup failure, redux

On 23.09.15 10:25, Robert J. Hansen wrote: >> $ gpg -v --keyserver hkp://pool.sks-keyservers.net --recv-key 0xD6B98E10 > > quorra:~ rjh$ gpg -v --keyserver hkp://pool.sks-keyservers.net > --recv-key 0xD6B98E10 > gpg: keyserver receive failed: No route to host > I can confirm that the exact abo

Re: Keyserver lookup failure, redux

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/23/2015 10:25 AM, Robert J. Hansen wrote: >> $ gpg -v --keyserver hkp://pool.sks-keyservers.net --recv-key >> 0xD6B98E10 > > quorra:~ rjh$ gpg -v --keyserver hkp://pool.sks-keyservers.net > --recv-key 0xD6B98E10 gpg: keyserver receive failed

Re: Keyserver lookup failure, redux

> $ gpg -v --keyserver hkp://pool.sks-keyservers.net --recv-key 0xD6B98E10 quorra:~ rjh$ gpg -v --keyserver hkp://pool.sks-keyservers.net --recv-key 0xD6B98E10 gpg: keyserver receive failed: No route to host > $ gpg-connect-agent --dirmngr 'keyserver --hosttable' /bye quorra:~ rjh$ gpg-conne

Re: Keyserver lookup failure, redux

On Tue, 22 Sep 2015 23:38, r...@sixdemonbag.org said: > Back in February I reported a bug that was preventing GnuPG 2.1.2 from > being able to look up certificates on the keyservers: Sorry, this got lost. Your mail back then was: Is there any explanation for this behavior, or is this a 2.1.2 b

Keyserver lookup failure, redux

Back in February I reported a bug that was preventing GnuPG 2.1.2 from being able to look up certificates on the keyservers: https://lists.gnupg.org/pipermail/gnupg-users/2015-February/052567.html I just looked at it again. 2.1.8 still has the same bug. Is there an idea for how to fix this? __