| 1 |
On Wednesday 24 February 2010 15:03:06 Willie Wong wrote: |
| 2 |
|
| 3 |
> Hum, also, try getting some debug output from gpg-agent: |
| 4 |
> |
| 5 |
> (1) 'killall gpg-agent' (and run ps aux to see if they are really |
| 6 |
> killed) |
| 7 |
> (2) Restart gpg-agent via |
| 8 |
> |
| 9 |
> eval 'gpg-agent --daemon --no-detach --debug-level guru --log-file |
| 10 |
> ~/gpg-agent.log' (3) Run gpg. |
| 11 |
> |
| 12 |
> Look at the content of ~/gpg-agent.log to see if anything is amiss. |
| 13 |
|
| 14 |
Thank you very much for persevering with me! :-) |
| 15 |
|
| 16 |
I changed your eval argument a bit and this is what I noticed: |
| 17 |
|
| 18 |
eval "$(gpg-agent --daemon --no-detach --debug-level guru --log-file gpg- |
| 19 |
agent.log)" |
| 20 |
gpg-agent[7276]: enabled debug flags: command mpi crypto memory cache memstat |
| 21 |
hashing assuan |
| 22 |
|
| 23 |
The log file shows: |
| 24 |
================================================ |
| 25 |
2010-02-24 20:32:01 gpg-agent[7276] listening on socket `/tmp/gpg- |
| 26 |
IX4A40/S.gpg-agent' |
| 27 |
2010-02-24 20:32:01 gpg-agent[7277] gpg-agent (GnuPG) 2.0.14 started |
| 28 |
2010-02-24 20:32:13 gpg-agent[7277] SIGINT received - immediate shutdown |
| 29 |
2010-02-24 20:32:13 gpg-agent[7277] gpg-agent (GnuPG) 2.0.14 stopped |
| 30 |
2010-02-24 20:32:13 gpg-agent[7277] random usage: poolsize=600 mixed=0 |
| 31 |
polls=0/0 added=0/0 |
| 32 |
outmix=0 getlvl1=0/0 getlvl2=0/0 |
| 33 |
2010-02-24 20:32:13 gpg-agent[7277] secmem usage: 0/32768 bytes in 0 blocks |
| 34 |
================================================ |
| 35 |
|
| 36 |
However, when I invoke gpg it looks for another socket ... different to the |
| 37 |
one that the agent is listening on. |
| 38 |
================================================ |
| 39 |
$ gpg -vv DATA/some_data.ods.gpg |
| 40 |
gpg: using character set `iso-8859-1' |
| 41 |
gpg: enabled debug flags: memstat |
| 42 |
:pubkey enc packet: version 3, algo 16, keyid <ZZZZZZZZZZZ> |
| 43 |
data: [2048 bits] |
| 44 |
data: [2045 bits] |
| 45 |
gpg: public key is XXXXXXXX |
| 46 |
gpg: using subkey XXXXXXXX instead of primary key YYYYYYYY |
| 47 |
|
| 48 |
You need a passphrase to unlock the secret key for |
| 49 |
user: "me <me@×××××.com>" |
| 50 |
gpg: using subkey XXXXXXXX instead of primary key YYYYYYYY |
| 51 |
2048-bit ELG key, ID XXXXXXXX, created 2010-01-25 (main key ID YYYYYYYY) |
| 52 |
|
| 53 |
can't connect to `/tmp/gpg-pNLb9Y/S.gpg-agent': No such file or directory |
| 54 |
gpg: can't connect to the agent - trying fall back |
| 55 |
can't connect to `/home/michael/.gnupg/S.gpg-agent': No such file or directory |
| 56 |
gpg: no running gpg-agent - starting one |
| 57 |
gpg-agent[7265]: enabled debug flags: assuan |
| 58 |
can't connect to `/home/michael/.gnupg/log-socket': Connection refused |
| 59 |
gpg: problem with the agent: No pinentry |
| 60 |
:encrypted data packet: |
| 61 |
length: 22577 |
| 62 |
mdc_method: 2 |
| 63 |
gpg: encrypted with 2048-bit ELG key, ID XXXXXXXX, created 2010-01-25 |
| 64 |
"me <me@×××××.com>" |
| 65 |
gpg: public key decryption failed: General error |
| 66 |
gpg: decryption failed: No secret key |
| 67 |
================================================ |
| 68 |
|
| 69 |
Why is this? Invoking gpg to decrypt different (encrypted) files always |
| 70 |
brings up that socket '/tmp/gpg-pNLb9Y/S.gpg-agent'. Shouldn't it be a |
| 71 |
different socket each time? |
| 72 |
|
| 73 |
Another thing that shows something has gone south is that pinentry no longer |
| 74 |
asks for a passphrase as shown above. Also, when I encrypt a file it still |
| 75 |
does not ask for my passphrase - it just encrypts the file! |
| 76 |
-- |
| 77 |
Regards, |
| 78 |
Mick |
Archives