On Thursday 25 February 2010 00:09:17 Willie Wong wrote: > On Wed, Feb 24, 2010 at 10:51:38PM +0000, Mick wrote:
> > Why is this? Invoking gpg to decrypt different (encrypted) files always > > brings up that socket '/tmp/gpg-pNLb9Y/S.gpg-agent'. Shouldn't it be a > > different socket each time? I noticed that this morning (after a reboot) it was looking for a different socket ... > Ack, let's do this one step at a time then. First let's try to figure > out the problem with the gpg-agent. [snip...] > In a new prompt, first paste the variable, then type gpg -vv *file* ============================================ $ gpg-agent --daemon --no-detach --debug-level guru --log-file gpg-agent.log gpg-agent[6740]: enabled debug flags: command mpi crypto memory cache memstat hashing assuan GPG_AGENT_INFO=/tmp/gpg-5Tgf3a/S.gpg-agent:6741:1; export GPG_AGENT_INFO; ============================================ This is now what the log shows: ============================================ 2010-02-25 06:45:53 gpg-agent[6740] listening on socket `/tmp/gpg-5Tgf3a/S.gpg-agent' 2010-02-25 06:45:53 gpg-agent[6741] gpg-agent (GnuPG) 2.0.14 started 2010-02-25 06:48:32 gpg-agent[6741] handler 0x98caa38 for fd 7 started gpg-agent[6741.7] DBG: -> OK Pleased to meet you gpg-agent[6741.7] DBG: <- RESET gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION ttyname=/dev/pts/3 gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION ttytype=rxvt gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION display=:0.0 gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION lc-ctype=C gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION lc-messages=C gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- OPTION allow-pinentry-notify gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- GETINFO cmd_has_option GET_PASSPHRASE repeat gpg-agent[6741.7] DBG: -> OK gpg-agent[6741.7] DBG: <- GET_PASSPHRASE --data --repeat=0 -- A7029FW0V2G567G225FST52689GV822Rf230gkw8F X X Please+enter+the+passphrase+to+unlock+the+secret+key+ for+the+OpenPGP+certificate:%0A%22me+<[email protected]>%22%0A2048-bit+ELG+key, +ID+XXXXXXXX,%0Acreated+2010-01-25+(main+key+ID+YYYYYYY).%0A 2010-02-25 06:48:32 gpg-agent[6741] DBG: agent_get_cache `A7029FW0V2G567G225FST52689GV822Rf230gkw8F'... 2010-02-25 06:48:32 gpg-agent[6741] DBG: ... miss 2010-02-25 06:48:32 gpg-agent[6741] starting a new PIN Entry gpg-agent[6741]: can't connect server: `ERR 67109133 can't exec `/usr/bin/pinentry-qt': No such file or directory' 2010-02-25 06:48:32 gpg-agent[6741] can't connect to the PIN entry module: IPC connect call failed 2010-02-25 06:48:32 gpg-agent[6741] command get_passphrase failed: No pinentry gpg-agent[6741.7] DBG: -> ERR 67108949 No pinentry <GPG Agent> gpg-agent[6741.7] DBG: <- [EOF] 2010-02-25 06:48:32 gpg-agent[6741] handler 0x98caa38 for fd 7 terminated ============================================ Why is it trying to call /usr/bin/pinentry-qt?! `ERR 67109133 can't exec `/usr/bin/pinentry-qt' Is this a valid binary these days, or an older qt3 version? I think it should be /usr/bin/pinentry: $ ls -la /usr/bin/pinentry lrwxrwxrwx 1 root root 12 Feb 24 07:01 /usr/bin/pinentry -> pinentry-qt4 Please note that the: "Please+enter+the+passphrase+to+unlock+the+secret+key" does not show up on the screen even when I use the gpg -vv option. -- Regards, Mick
