[PATCH 1/1] gpg-agent: add new option --cancel-card-pinentry

Curt Brune curt at brune.net
Fri Dec 16 19:41:30 CET 2016

On Fri, Dec 16, 2016 at 9:27 AM, Werner Koch <wk at gnupg.org> wrote:

> On Fri, 16 Dec 2016 08:48, neal at walfield.org said:
> > would iterate over all of the PK-ESK blocks, determine whether the
> > user could potentially decrypt them, and then rank them according to
> > the expected ease with which the user could do that.  One criteria
> Right, we have this comment in gpg:
>       /* FIXME: Store this all in a list and process it later so that
>          we can prioritize what key to use.  This gives a better user
>          experience if wildcard keyids are used.  */
​That is the problem exactly.  I saw that gpg tried the keyids one by

> Curt: I would change the code to have such an option in gpg and not in
> gpg-agent.  Thus the flag needs to be stored in the CTRL object which is
> initialized from a new Assuan OPTION (similar to pinentry-mode).
​Thanks for the suggestion. I will look into that.

> The option name in gpg should also reflect what it is about and not how
> it technically works.  Something with like --no-card-change-prompt.
​Indeed, the option name is bad.  I went through 3 or 4 different names,
none of them very good.​  The naming took the most time :)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20161216/8e1a131c/attachment.html>

More information about the Gnupg-devel mailing list