1 |
On Thursday 25 February 2010 00:09:17 Willie Wong wrote: |
2 |
> On Wed, Feb 24, 2010 at 10:51:38PM +0000, Mick wrote: |
3 |
|
4 |
> > Why is this? Invoking gpg to decrypt different (encrypted) files always |
5 |
> > brings up that socket '/tmp/gpg-pNLb9Y/S.gpg-agent'. Shouldn't it be a |
6 |
> > different socket each time? |
7 |
|
8 |
I noticed that this morning (after a reboot) it was looking for a different |
9 |
socket ... |
10 |
|
11 |
> Ack, let's do this one step at a time then. First let's try to figure |
12 |
> out the problem with the gpg-agent. |
13 |
[snip...] |
14 |
|
15 |
> In a new prompt, first paste the variable, then type gpg -vv *file* |
16 |
|
17 |
============================================ |
18 |
$ gpg-agent --daemon --no-detach --debug-level guru --log-file gpg-agent.log |
19 |
gpg-agent[6740]: enabled debug flags: command mpi crypto memory cache memstat |
20 |
hashing assuan |
21 |
GPG_AGENT_INFO=/tmp/gpg-5Tgf3a/S.gpg-agent:6741:1; export GPG_AGENT_INFO; |
22 |
============================================ |
23 |
|
24 |
This is now what the log shows: |
25 |
============================================ |
26 |
2010-02-25 06:45:53 gpg-agent[6740] listening on socket |
27 |
`/tmp/gpg-5Tgf3a/S.gpg-agent' |
28 |
2010-02-25 06:45:53 gpg-agent[6741] gpg-agent (GnuPG) 2.0.14 started |
29 |
2010-02-25 06:48:32 gpg-agent[6741] handler 0x98caa38 for fd 7 started |
30 |
gpg-agent[6741.7] DBG: -> OK Pleased to meet you |
31 |
gpg-agent[6741.7] DBG: <- RESET |
32 |
gpg-agent[6741.7] DBG: -> OK |
33 |
gpg-agent[6741.7] DBG: <- OPTION ttyname=/dev/pts/3 |
34 |
gpg-agent[6741.7] DBG: -> OK |
35 |
gpg-agent[6741.7] DBG: <- OPTION ttytype=rxvt |
36 |
gpg-agent[6741.7] DBG: -> OK |
37 |
gpg-agent[6741.7] DBG: <- OPTION display=:0.0 |
38 |
gpg-agent[6741.7] DBG: -> OK |
39 |
gpg-agent[6741.7] DBG: <- OPTION lc-ctype=C |
40 |
gpg-agent[6741.7] DBG: -> OK |
41 |
gpg-agent[6741.7] DBG: <- OPTION lc-messages=C |
42 |
gpg-agent[6741.7] DBG: -> OK |
43 |
gpg-agent[6741.7] DBG: <- OPTION allow-pinentry-notify |
44 |
gpg-agent[6741.7] DBG: -> OK |
45 |
gpg-agent[6741.7] DBG: <- GETINFO cmd_has_option GET_PASSPHRASE repeat |
46 |
gpg-agent[6741.7] DBG: -> OK |
47 |
gpg-agent[6741.7] DBG: <- GET_PASSPHRASE --data --repeat=0 -- |
48 |
A7029FW0V2G567G225FST52689GV822Rf230gkw8F X X |
49 |
Please+enter+the+passphrase+to+unlock+the+secret+key+ |
50 |
for+the+OpenPGP+certificate:%0A%22me+<me@×××××.com>%22%0A2048-bit+ELG+key, |
51 |
+ID+XXXXXXXX,%0Acreated+2010-01-25+(main+key+ID+YYYYYYY).%0A |
52 |
2010-02-25 06:48:32 gpg-agent[6741] DBG: agent_get_cache |
53 |
`A7029FW0V2G567G225FST52689GV822Rf230gkw8F'... |
54 |
2010-02-25 06:48:32 gpg-agent[6741] DBG: ... miss |
55 |
2010-02-25 06:48:32 gpg-agent[6741] starting a new PIN Entry |
56 |
gpg-agent[6741]: can't connect server: `ERR 67109133 can't exec |
57 |
`/usr/bin/pinentry-qt': No such file or directory' |
58 |
2010-02-25 06:48:32 gpg-agent[6741] can't connect to the PIN entry module: IPC |
59 |
connect call failed |
60 |
2010-02-25 06:48:32 gpg-agent[6741] command get_passphrase failed: No pinentry |
61 |
gpg-agent[6741.7] DBG: -> ERR 67108949 No pinentry <GPG Agent> |
62 |
gpg-agent[6741.7] DBG: <- [EOF] |
63 |
2010-02-25 06:48:32 gpg-agent[6741] handler 0x98caa38 for fd 7 terminated |
64 |
============================================ |
65 |
|
66 |
Why is it trying to call /usr/bin/pinentry-qt?! |
67 |
|
68 |
`ERR 67109133 can't exec `/usr/bin/pinentry-qt' |
69 |
|
70 |
Is this a valid binary these days, or an older qt3 version? I think it should |
71 |
be /usr/bin/pinentry: |
72 |
|
73 |
$ ls -la /usr/bin/pinentry |
74 |
lrwxrwxrwx 1 root root 12 Feb 24 07:01 /usr/bin/pinentry -> pinentry-qt4 |
75 |
|
76 |
Please note that the: "Please+enter+the+passphrase+to+unlock+the+secret+key" |
77 |
does not show up on the screen even when I use the gpg -vv option. |
78 |
-- |
79 |
Regards, |
80 |
Mick |