pinentry's new window titles could be more (less?) informative

Daniel Kahn Gillmor dkg at
Fri Oct 13 01:03:43 CEST 2017

On Fri 2017-09-29 11:00:51 +0200, Werner Koch wrote:
> On Thu, 28 Sep 2017 20:03, rjh at said:
>> So my question is, yes, I see what the intent is here: to give users
>> some assurance their PIN is being requested by the program they expect.
> Actually the reason I implemented this was to see the ssh invocation.  I
> have a few cron jobs connecting to other boxes running and thus it is
> interesting to see which kicked the pinentry.

I understand this desire, but i think the concerns raised in the rest of
this thread still stand.

Can we figure out some path forward that will make this more useful and
less intimidating?

I've just pushed a few minor cleanups to pinentry that shouldn't
interfere with the ssh use case you describe, but don't do anything
significant to fix the other problems mentioned here.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: </pipermail/gnupg-devel/attachments/20171012/1898c536/attachment.sig>

More information about the Gnupg-devel mailing list