Hi Jean-Luc & Peter: Am 26.08.09 22:35 schrieb(en) Jean-Luc Coulon (f5ibh):
[jean-luc tangerine] % gpg2 --sign -a You need a passphrase to unlock the secret key for user: "Jean-Luc Coulon (f5ibh) <jean-luc coulon wanadoo fr>" 1024-bit DSA key, ID 3CC69CD0, created 2001-09-07 gpg: problem with the agent: No pinentry gpg: no default secret key: General error gpg: signing failed: General error
There's something broken with gpg2, afaict...
I use seahorse normally.
Please be sure that you use *either* gpg-agent *or* the agent coming with seahorse (seahorse-agent?). I prefer using gpg-agent; as iirc seahorse-agent doesn't support the ncurses terminal if, and doesn't support all stuff needed by gpgsm.
What you could do for testing:(1) Terminate all running gpg-agent's (killall). Run "ps auxw | grep agent" to check they are *really* gone (on my Ubuntu box, 'killall gpg-agent' left a Zombie, which didn't do any harm).
(2) Run the command "gpg-agent --daemon --no-detach --debug-level guru --log-file ./gpg-agent.log". It will give you a line reading like "GPG_AGENT_INFO=/tmp/gpg-ZnjGbt/S.gpg-agent:7049:1; export GPG_AGENT_INFO;". Enter this line.
(3) Now run "gpg2 --sign -a". If I give the agent a bad (non-existent) pinentry, it will print out information about that both in the gpg2 session and in the file ./gpg-agent.log. Maybe that gives some more insight.
You could also try to use a different pinentry (like the qt version) - in the past, there were issues with suid-root Gtk+ applications.
Hope this helps, Albrecht.
Attachment:
pgpwLS6TyOEM3.pgp
Description: PGP signature