Cc: gnupg-users@gnupg.org
Subject: Re: FW: gpg-agent connection errors
ATTENTION: This email came from an external source. Do not open attachments or
click on links from unknown or unexpected emails.
On Fri, 22 May 2020 03:18, Ángel said:
> how this AF_UNIX socket is actually implemented on G
On Freitag, 22. Mai 2020 10:48:55 CEST Werner Koch via Gnupg-users wrote:
> On Fri, 22 May 2020 03:18, Ángel said:
> > how this AF_UNIX socket is actually implemented on Gpg4win (as a named
> > pipe, perhaps?), but your issues might be related to having it on a
>
> It is a regular file with a nonc
On Fri, 22 May 2020 03:18, Ángel said:
> how this AF_UNIX socket is actually implemented on Gpg4win (as a named
> pipe, perhaps?), but your issues might be related to having it on a
It is a regular file with a nonce and a port. The server listens on
localhost:THATPORT for connections and checks
On 2020-05-20 at 18:22 +, Kent A. Larsen wrote:
> I've adding logging to our gpg-agent.conf file, and when these errors
> occur the gpg-agent log file has the following error:
> 2020-05-18 09:36:07 gpg-agent[3800] error binding socket to '\\Neofs1
> \Userapps\Apps\GnuPG\Keys\S.gpg-agent': Unkno
Werner,
If that's the case, then why do we continue to intermittently get the following
messages when issuing a command to sign+encrypt (or decrypt) a file?
gpg: can't connect to the agent: IPC connect call failed
gpg: keydb_search failed: No agent running
gpg: skipped "0x8A811544": No agent run
