Beta for 2.1.1 available
wk at gnupg.org
Mon Nov 24 13:43:09 CET 2014
On Mon, 24 Nov 2014 10:55, kristian.fiskerstrand at sumptuouscapital.com
> Is this limited to GPA? I seem to also encounter issues directly from
> CLI to this effect.
Yes. The thing is that GPA makes direct use of the gpgkeys_foo helpers
and bypasses gpg for keyserver access. Now with 2.1 we do not have the
gpgkeys_foo helpers anymore and thus export must go through gpg. This
is not a big problem, given that GPGME support this for quite some time
You problem must be a different one.
$ ../g10/gpg2 --send-key 0x0B7F8B60E3EDFAE3
gpg: WARNING: unsafe permissions on homedir '/home/wk/b/gnupg/tmp'
gpg: NOTE: THIS IS A DEVELOPMENT VERSION!
gpg: It is only intended for test purposes and should NOT be
gpg: used in a production environment or with production keys!
gpg: sending key E3EDFAE3 to hkp server zimmermann.mayfirst.org
$ grep zimmerman *conf
> 2014-11-24 10:52:40 dirmngr[29131.0] assuan_inquire failed: End of file
> 2014-11-24 10:52:40 dirmngr[29131.0] command 'KS_PUT' failed: End of file
gpg died after sending the command to dirmngr? Add --debug 1024 to the
gpg invocation to check this.
> libassuan version is 2.1.2.
Mine is 2.1.3 but the changes are only for Windows.
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gnupg-users