-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi, I'm using GnuPG 2.0.30 (installed for Windows 8.1 by Gpg4win 2.3.1). If I run gpg2 --no-options --keyserver keys.gnupg.net --refresh-keys I get "gpg: fordere Schl³ssel F0D6B1E0 von ldap-Server keyserver.pgp.com an" which translates to something like "gpg: request key F0D6B1E0 from ldap-Server keyserver.pgp.com" All other keys are updated from keyserver.pgp.com as requested but for key F0D6B1E0 its preferred key server ldap://keyserver.pgp.com is used. I can use gpg2 --no-options --keyserver keys.gnupg.net --keyserver-options no-honor-keyserver-url --refresh-keys to only use keys.gnupg.net but from the manual https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-Options.html > honor-keyserver-url When using --refresh-keys, if the key in > question has a preferred keyserver URL, then use that preferred > keyserver to refresh the key from. In addition, if > auto-key-retrieve is set, and the signature being verified has a > preferred keyserver URL, then use that preferred keyserver to > fetch the key from. Note that this option introduces a "web bug": > The creator of the key can see when the keys is refreshed. Thus > this option is not enabled by default. I thought that honor-keyserver-url is disabled by default (for very good reasons) and I'm therefore surprised that I have to specify no-honor-keyserver-url explicitly. Can somebody comment on this issue? Just two more short questions by me: - - Is there a way (for me or you) to fix the encoding of the gpg output (the German Umlaute are not properly displayed, for example in "Schlüssel", "unverändert"...)? - - Already in 2014 was reported http://wald.intevation.org/tracker/?func=detail&atid=126&aid=6528&group_id=11 that the --workdir option is not working in gnupg 2.0 and it still doesn't work in gnupg 2.0.30. Is there a chance that it will work in coming 2.0.X versions or do I have to switch to 2.1 (I was told that it is working there)? Of course I can set the GNUPGHOME system variable but I found having an command line option more convenient. It took me quite some time to find out that there was a problem after I updated from gnupg 1.4, at least an error/warning should be provided so that others don't run into the same pitfall. Kind regards, Hauke -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlcmXtwACgkQjz8jfoq989daMgCfdloQf2i6gtyM//sqxQPHPZxB 8loAn0oRWxTPsdwCjtHwgigfMO9YvGfu =d7/G -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
