Using loopback pin entry with GnuPG 2.1

[Werner Koch]

On Sat,  5 Nov 2016 11:06, vinay_sajip at yahoo.co.uk said:

> As I mentioned in my post, the allow-loopback-pinentry option has
> already been specified in gpg-agent.conf. As to the version of GnuPG

Not in the version of the agent you are running.  Look at the log
message:

> Thread-13  gpg: DBG: chan_5 -> OPTION pinentry-mode=loopback
> Thread-13  gpg: DBG: chan_5 <- ERR 67108924 Not supported <GPG Agent>

and the code producing this:

  else if (!strcmp (key, "pinentry-mode"))
    {
      int tmp = parse_pinentry_mode (value);
      if (tmp == -1)
        err = gpg_error (GPG_ERR_INV_VALUE);
      else if (tmp == PINENTRY_MODE_LOOPBACK && !opt.allow_loopback_pinentry)
        err = gpg_error (GPG_ERR_NOT_SUPPORTED);
      else
        ctrl->pinentry_mode = tmp;
    }
  [...]
  else
    err = gpg_error (GPG_ERR_UNKNOWN_OPTION);

Thus you will see the error "Not supported" (GPG_ERR_NOT_SUPPORTED) only
if opt.allow_loopback_pinentry (this variable is set from the conf file)
is not set.  I suggest to double check your setup.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: </pipermail/attachments/20161105/29ce93d8/attachment.sig>