Re: [gentoo-user] gnupg fails to decrypt on kmail

[Mick <michaelkintzios@gmail.com>]

On Wednesday 24 February 2010 15:03:06 Willie Wong wrote:

> Hum, also, try getting some debug output from gpg-agent:
> 
> (1) 'killall gpg-agent'   (and run ps aux to see if they are really
> killed)
> (2) Restart gpg-agent via
> 
>  eval 'gpg-agent --daemon --no-detach --debug-level guru --log-file
>  ~/gpg-agent.log' (3) Run gpg.
> 
> Look at the content of ~/gpg-agent.log to see if anything is amiss.

Thank you very much for persevering with me!  :-)

I changed your eval argument a bit and this is what I noticed:

eval "$(gpg-agent --daemon --no-detach --debug-level guru --log-file gpg-
agent.log)"
gpg-agent[7276]: enabled debug flags: command mpi crypto memory cache memstat 
hashing assuan

The log file shows:
================================================
2010-02-24 20:32:01 gpg-agent[7276] listening on socket `/tmp/gpg-
IX4A40/S.gpg-agent'
2010-02-24 20:32:01 gpg-agent[7277] gpg-agent (GnuPG) 2.0.14 started
2010-02-24 20:32:13 gpg-agent[7277] SIGINT received - immediate shutdown
2010-02-24 20:32:13 gpg-agent[7277] gpg-agent (GnuPG) 2.0.14 stopped
2010-02-24 20:32:13 gpg-agent[7277] random usage: poolsize=600 mixed=0 
polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
2010-02-24 20:32:13 gpg-agent[7277] secmem usage: 0/32768 bytes in 0 blocks
================================================

However, when I invoke gpg it looks for another socket ... different to the 
one that the agent is listening on.
================================================
$ gpg -vv DATA/some_data.ods.gpg
gpg: using character set `iso-8859-1'
gpg: enabled debug flags: memstat
:pubkey enc packet: version 3, algo 16, keyid <ZZZZZZZZZZZ>
        data: [2048 bits]
        data: [2045 bits]
gpg: public key is XXXXXXXX
gpg: using subkey XXXXXXXX instead of primary key YYYYYYYY

You need a passphrase to unlock the secret key for
user: "me <me@gmail.com>"
gpg: using subkey XXXXXXXX instead of primary key YYYYYYYY
2048-bit ELG key, ID XXXXXXXX, created 2010-01-25 (main key ID YYYYYYYY)

can't connect to `/tmp/gpg-pNLb9Y/S.gpg-agent': No such file or directory
gpg: can't connect to the agent - trying fall back
can't connect to `/home/michael/.gnupg/S.gpg-agent': No such file or directory
gpg: no running gpg-agent - starting one
gpg-agent[7265]: enabled debug flags: assuan
can't connect to `/home/michael/.gnupg/log-socket': Connection refused
gpg: problem with the agent: No pinentry
:encrypted data packet:
        length: 22577
        mdc_method: 2
gpg: encrypted with 2048-bit ELG key, ID XXXXXXXX, created 2010-01-25
      "me <me@gmail.com>"
gpg: public key decryption failed: General error
gpg: decryption failed: No secret key
================================================

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?

Another thing that shows something has gone south is that pinentry no longer 
asks for a passphrase as shown above.  Also, when I encrypt a file it still 
does not ask for my passphrase - it just encrypts the file!
-- 
Regards,
Mick