[PATCH] --batch should imply --pinentry-mode=loopback???

Daniel Kahn Gillmor dkg at fifthhorseman.net
Sat May 2 03:33:34 CEST 2015

This for bringing this up!

On Fri 2015-05-01 03:30:36 -0400, NIIBE Yutaka wrote:
> These are fix candidates for the issue 1928:
>     https://bugs.gnupg.org/gnupg/issue1928
> In g10/passphrase.c, there is a condtion like:
>    (opt.batch || opt.pinentry_mode == PINENTRY_MODE_LOOPBACK)
> ... which makes me wonder if there is a case people want to specify
> options with --batch --pinentry-mode=ask/cancel.

There is definitely a case where we want both --batch and

Consider a graphical GnuPG frontend that does key generation.

Ideally, that frontend should not need to ever touch the user's
password, or to implement any password-entry UI.  However, it should be
able to select appropriate values for the initial user ID and for any
sort of key parameters (usage flags, etc) that are relevant to the use

Please do not remove the ability to use --gen-key --batch with
--pinentry-mode=ask !

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: </pipermail/attachments/20150501/aa71afa5/attachment.sig>

More information about the Gnupg-devel mailing list