[Gpg4win-users-en] Gpg4win 2.2.3: gpg --refresh-keys no longer working with hkps
Dr. Peter Voigt
pvoigt at uos.de
Mon Dec 8 00:16:19 CET 2014
On Sun, 07 Dec 2014 19:27:33 -0300
Faramir <faramir.cl at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> El 05-12-2014 a las 4:54, Bernhard Reiter escibió:
> > Peter,
> > Can you run it with the debugging options outlined in the post
> > above to confirm the analysis?
> > Thanks, Bernhard
> Mmmm... I tried to refresh a key from keyservers using GPGShell, and
> it didn't work (no data found on keyservers, and it tried in several
> of them). GPA couldn't refresh it. But Enigmail could. I don't know
> how Peter activated the debug options, but I'd like to do it too,
> since it seems it magically solved the problem.
> By the way, I'm also using Win 7 64bits, GPG4Win 2.2.3
> Best Regards
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> -----END PGP SIGNATURE-----
> Gpg4win-users-en mailing list
> Gpg4win-users-en at wald.intevation.org
I added following lines to gpg.conf:
This makes gpg a bit more verbose. I just tested "gpg --refresh-keys"
only, because I never use a different way for keyring refresh.
On my Win 7 Pro SP1 (amd64) the above command is working now with
version 2.2.3. I do not know why it did work initially. But Andre's
suggestion is a good point: The there might have been envolved a
different keyserver out of the pool. Maybe you should try several times
with a considerable time gap between your attempts.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 836 bytes
Desc: not available
More information about the Gpg4win-users-en