Using loopback pin entry with GnuPG 2.1

[Werner Koch]

On Fri,  4 Nov 2016 11:11, vinay_sajip at yahoo.co.uk said:

>
> The second window now shows traffic with the agent, e.g.:
>
> [client at fd 4 connected (local)]
> 4 - 2016-11-04 10:04:10  started
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_6 -> OK Pleased to meet you, process 1897
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_4 <- OK Pleased to meet you, process 1897
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_4 -> GETINFO pid
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_6 <- GETINFO pid
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_6 -> D 1897
> 4 - 2016-11-04 10:04:10 gpg-agent[1897]: DBG: chan_4 <- D 1897

That is gpg-agent making a connection to itself to see whether its
socket is still connected to self.  This is done once a minute.

It seems your gpg is not using that agent.

You can add "--debug ipc" to gpg to get gpg's site of the communication.


Salam-Shalom,

   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/20161104/6592f819/attachment-0001.sig>