Re: Fails to sign a message after gnupg2/gpgsm upgrade

Hi Albrecht!

On Aug 26, 2009, at  1:42 PM, Albrecht Dreß wrote:
Hi Jean-Luc:

Am 26.08.09 14:02 schrieb(en) Jean-Luc Coulon (f5ibh):
I've updated gnupg2/gpgsm from 2.0.11-1 to 2.0.12-1 (Debian sid)

Since that Balsa refuses to sign a message, there is a popup saying gpgsm is unable to sign the message because the passphrase is wrong (the passphrase is cached in my case).

I'm having the same issue.

Hmm, that's really strange. It sounds a little bit as if the agent communication is broken. Can you please try the following:

- in a shell, run 'echo $GPG_AGENT_INFO' which should show something like "/tmp/gpg-EKhTLm/S.gpg-agent:<pid>:1". Verify that the pipe and the process (<pid>) exist;

The socket and process both exist.

- from the shell, run "gpg --sign" which should pop up the passphrase dialogue (pinentry). If it doesn't, there is a communication problem between gpg and the agent;

OK, no popup, just "You need a passphrase to unlock the secret key for..." on the console.

Downgrading to gnupg2.x86_64 0:2.0.11-1.fc11 (from gnupg2.x86_64 0:2.0.12-1.fc11) seems to have fixed it. Other versions are:




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]