gpg-agent/pinentry: How to verify calling application

Hartmut Knaack knaack.h at
Mon Jul 17 00:47:23 CEST 2017

Shawn K. Quinn schrieb am 16.07.2017 um 09:48:
> On 07/15/2017 09:02 AM, Hartmut Knaack wrote:
>> Hi,
>> on my machine running Linux and a recent KDE/Plasma, pinentry-qt
>> occasionally starts right after logging in and asks for my passphrase.
>> Is there any way to track down, which process asks gpg-agent for my private
>> key? Preferably, I would like pinentry to inform, which process actually is
>> the source of the key request.
>> Thanks
> This is a bit of a "duct tape"  but you could try:
> # chmod 000 `which pinentry-qt`
> then reboot and see what program throws an error (besides GnuPG).
> Don't forget to change it back when done testing.

Thanks for the hint. Unfortunately, it happens just very occasionally,
and I haven't figured out yet, what the reason may be. I have been logging
on at least ten times, and even fully rebooted five times today, without
getting such a request.
I have now installed the git version of pinentry and will just wait for
this issue to happen next.


> _______________________________________________
> Gnupg-users mailing list
> Gnupg-users at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xFAC89148.asc
Type: application/pgp-keys
Size: 3086 bytes
Desc: not available
URL: </pipermail/attachments/20170717/b7a626b2/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20170717/b7a626b2/attachment.sig>

More information about the Gnupg-users mailing list