gpgsm with empty passphrase?

Jens Lechtenboerger lechten at wi.uni-muenster.de
Thu Oct 15 17:31:43 CEST 2015


Hi there,

I fail to use gpgsm from 2.1.9 with empty passphrases for test keys.
(2.0.x works with the workaround described there:
https://bugs.gnupg.org/gnupg/issue2126)

I’m using gpgsm compiled via “make -f build-aux/speedo.mk  native”
with exported PATH and LD_LIBRARY_PATH.

In the directory with test keys I also created gpg-agent.conf with
debug settings.  When decrypting as follows
$ gpgsm --homedir <dir-with-test-keys> --decrypt /tmp/gpgsm.enc
I see the following debug message from gpg-agent 2.1.9:

--8<---------------cut here---------------start------------->8---
can't connect to the PIN entry module '/home/lechten/local/gnupg-2.1.9/PLAY/inst/bin/pinentry': IPC "connect" Aufruf fehlgeschlagen
--8<---------------cut here---------------end--------------->8---

IMO, that path should not be used or pinentry should be built.
When adding a pinentry option to gpg-agent.conf, I get the
following debug messages from gpg-agent after just hitting return or
clicking “OK” in the pinentry window (as I want to use an empty
passphrase):

--8<---------------cut here---------------start------------->8---
DBG: connection to PIN entry established
DBG: chan_5 -> INQUIRE PINENTRY_LAUNCHED 10817
DBG: chan_5 <- END
DBG: error calling pinentry: No passphrase given <GPG Agent>
failed to unprotect the secret key: No passphrase given
failed to read the secret key
command 'PKDECRYPT' failed: No passphrase given
DBG: chan_5 -> ERR 67109041 No passphrase given <GPG Agent>
DBG: chan_5 <- [eof]
--8<---------------cut here---------------end--------------->8---

Am I doing something wrong or is this a bug?

Best wishes
Jens




More information about the Gnupg-users mailing list