Page MenuHome GnuPG
Create Task
Maniphest T1994

gpg2 --pinentry-mode=loopback without allow-loopback-pinentry
Closed, ResolvedPublic
Actions

Description

If allow-loopback-pinentry is not in gpg-agent.conf, then loopback pinentry mode
is not enabled. In this case, gpg should either issue a warning or an error if
--pinentry-mode=loopback is specified.

How to recreate:

  1. Make sure ~/.gnupg/gpg-agent.conf does not include allow-loopback-pinentry
  2. Run echo | gpg2 --pinentry-mode=loopback -s -a

Observed results:

  A normal pinentry (i.e., mode=ask) is shown.

Expected results:

A warning or error that loopback mode is not possible.

Event Timeline

neal added projects: gnupg, Bug Report.Jun 1 2015, 5:43 PM
neal added a subscriber: neal.
neal closed this task as Resolved.Nov 20 2015, 1:13 PM
neal claimed this task.

It seems this now works. In fact the code suggests that it should have detected
this condition since at least 2013 so I don't know what the actual issue was.

$ echo | gpg2 --pinentry-mode=loopback -s -a
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: setting pinentry mode 'loopback' failed: Not supported