[prev in list] [next in list] [prev in thread] [next in thread]
List: gpg4win-users-en
Subject: Re: [Gpg4win-users-en] Kleopatra UI server issues
From: Oscar Olsson <m8585 () abc ! se>
Date: 2013-11-29 9:26:31
Message-ID: alpine.BSO.2.11.1311291018190.12808 () orm ! abc ! se
[Download RAW message or body]
On Thu, 28 Nov 2013, Werner Koch wrote:
WK> On Thu, 28 Nov 2013 16:01, m8585@abc.se said:
WK>
WK> > To me, this suggests that the UI server isn't actually using IP for
WK> > communication, but rather some kind of flat file based method? Or is it
WK> > just to figure out what port it's listening to?
WK>
WK> Right, the file give the port and an authentication cookie. Thus
WK> standard file system permissions are used to protect the connection.
WK>
WK> Does it work if you use gpa? Open a command window and run "gpa
WK> --daemon" gpa has no selftest but offers the same functionality as
WK> Kleopatra.
Nope it does not.
GPA gives the following output:
C:\Users\SWEOLO>gpa --daemon
chan_00000464 -> OK Pleased to meet you
As I understand it, it communicates with the gpg-agent. For some reason,
there seems to be a basic file I/O problem or similar, since it uses a
file as a socket.
This is what I see in the gpg-agent.exe output if I run it from CLI:
C:\Program Files (x86)\GNU\GnuPG>gpg-agent.exe --debug 9 --daemon
gpg-agent[5136]: NOTE: no default option file
`C:\Users\SWEOLO\AppData\Roaming\g
nupg\gpg-agent.conf'
gpg-agent[5136]: enabled debug flags: command
gpg-agent[5136]: listening on socket
`C:\Users\SWEOLO\AppData\Roaming\gnupg\S.gp
g-agent'
set
GPG_AGENT_INFO=C:\Users\SWEOLO\AppData\Roaming\gnupg\S.gpg-agent;5136;1
gpg-agent[5136]: gpg-agent (GnuPG) 2.0.22 started
gpg-agent[5136]: DBG: returning notify handle 000003FC
gpg-agent[5136]: handler 0x1980 for fd 1032 started
gpg-agent[5136]: Assuan processing failed: Input/output error
gpg-agent[5136]: handler 0x1980 for fd 1032 terminated
gpg-agent[5136]: handler 0x150c for fd 1044 started
gpg-agent[5136]: Assuan processing failed: Input/output error
gpg-agent[5136]: handler 0x150c for fd 1044 terminated
gpg-agent[5136]: handler 0xc84 for fd 1064 started
gpg-agent[5136]: handler 0xc84 for fd 1064 terminated
gpg-agent[5136]: handler 0x4b8 for fd 1032 started
gpg-agent[5136]: handler 0x4b8 for fd 1032 terminated
To me, this is probably a pretty common error under Windows 7? Has anyone
else seen this? Any fix/work-around?
//Oscar
_______________________________________________
Gpg4win-users-en mailing list
Gpg4win-users-en@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/gpg4win-users-en
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic