I have GnuPG working in Licq but I have to put my GnuPG passphrase in the Licq configs for this to work. For this reason, I use a different key and passphrase in Licq than what I use for email. An alternative to doing things this way is to use gpg-agent, which is not available in stable versions of GnuPG but only in the experimental branch. I was unable to compile gpg-agent on the newer compilers so that I could avoid using the 'gpg' found in the experimental branch, so I tried using the experimental GnuPG (and accepted the risk) version and although I seemed to have gpg-agent working, Licq would not see the cached GnuPG passphrase.
I went back to stable GnuPG and later found a download site for a Debian "newpg" package that has gpg-agent, thus allowing me to keep stable GnuPG while having the option of using gpg-agent: http://ma2geo.mathematik.uni-karlsruhe.de/public-debian/sarge/ I downloaded and installed the newpg and libksba0 packages and tried gpg-agent again with 'eval "$(gpg-agent --daemon)"' (with the double quotes not the outer single quotes) and I can get pinentry to ask me for my passphrase and it does seem as though gpg-agent is storing the passphrase, but Licq is not seeing it. This is what I have in licq_gpg.conf: [gpg] passphrase = It does not work. Does anyone know what might be wrong? I don't think it is a big problem if I put my passphrase in the config, but it would be better not to have to do that. Oh one more oddity is that when I enter my passphrase, pinentry asks for two passphrases and the first one is not the passphrase for the key I use with Licq. This is the command I use: echo "test" | gpg -ase -r 0x2B0E07C6 | gpg the key shown is the one I use with Licq, but the first passphrase pinentry requests is not one used with that key. I do not have a default key set in my gnupg config. I will try setting the Licq key as the default to see what happens. -- Andrew GnuPG Key ID 0xF1EA7653
pgp00000.pgp
Description: PGP signature
