'No pinentry' error (--pinentry-mode loopback with --delete-secret-and-public-key)

Dashamir Hoxha dashohoxha at gmail.com
Wed May 11 04:42:40 CEST 2016

On Wed, May 11, 2016 at 1:20 AM, Carola Grunwald <caro at nymph.paranoici.org>
> When an application creates a key it also has to get it deleted.
> With the 1.4 branch I interacted with the GnuPG process completely
> unattended through standard-I/O pipes, which now are replaced by the
> pinentry mechanism, where redirections fail.

Pinentry may be a good feature, but there should be an easy way to bypass
or disable it.

> Many thanks.  But I'm on Windows, dependent on binaries.  Without
> nightly builds I have to wait for the next release, or try to
> crosscompile it in my Debian VM, which I doubt to manage.

Maybe the realse schedule should include alpha and beta, before making a
stable release, so that the community has a change to test and find out any
problems, which can hopefully be fixed before the final release.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20160511/63a143c0/attachment.html>

More information about the Gnupg-users mailing list