Hello, Le jeudi 2 juin 2011, Peter Eisentraut a écrit : > On tor, 2011-06-02 at 18:44 +0200, Philippe Latu wrote: > > Hello, > > > > Le jeudi 2 juin 2011, vous avez écrit : > > > On tor, 2011-05-12 at 22:08 +0200, Philippe Latu wrote: > > > > The following symlink should be added during package installation to > > > > fit kmail needs. > > > > Without it, the mail client sends a "bad passphrase" error message > > > > without prompting anything. > > > > > > > > ln -s /usr/bin/pinentry-qt4 /usr/bin/pinentry-qt > > > > > > > > Message signing works perfectly when this symlink exists. > > > > > > Why would kmail call pinentry directly, or hardcode the use of > > > pinentry-qt? > > > > I browsed kmail configuration parameters and pinentry is not mentionned. > > The only tool specified in the message signing parameters is OpenPGP/gpg. > > > > I don't know if another kde tool use pinentry. KDEWallet doesn't for > > instance. > > > > The only thing I am sure of is that this link is necessary when kmail has > > to sign a message like this one ... > > The way this normally works is that kmail calls gpg, gpg calls > gpg-agent, gpg-agent calls pinentry, which is an alternative pointing > to /usr/bin/pinentry-something. If that doesn't work, you either have > something wrong configured for pinentry-program in > ~/.gnupg/gpg-agent.conf, which would be a user error
That's it and the user error is mine. I had edited the .gnupg/gpg-agent.conf file in 2006 and completely forgot about the entry "pinentry-program /usr/bin/pinentry-qt" since then. > , or the alternative > points to something wrong, which could be a user or a packaging error. > In any case, I think the original assertion that kmail needs pinentry-qt > specifically is wrong. I was wrong. Sorry for disturbing you. This bug can be closed. Regards, -- - Philippe Latu philippe.latu(at)linux-france.org http://www.linux-france.org/~platu (GPG|PGP) KeyId 0x742A6424 - http://www.linux-france.org/~platu/key.asc
signature.asc
Description: This is a digitally signed message part.
