Re: S/MIME signing fails on a SUSE 9.3 system
Karsten Künne <[email protected]> Thu, 2 Jun 2005 18:12:09 -0400
| Newsgroups | gmane.comp.encryption.gpg.gpa.devel |
|---|---|
| Organization | Renaissance Technologies Corp. |
| Message-ID | <[email protected]> |
On Thursday 02 June 2005 16:55, Karsten Künne wrote: > On Thursday 02 June 2005 16:42, Karsten Künne wrote: > > On Thursday 02 June 2005 06:08, Werner Koch wrote: > > > On Tue, 31 May 2005 14:37:44 -0400, Karsten Künne said: > > > > The gpg-agent is running and GPG_AGENT_INFO is set correctly. Does > > > > anybody know what's going on here? > > > > > > It does not find pinentry for reasons I don't know. The easiest > > > workaround is to add a line like > > > > > > pinentry-program /usr/lib/pinentry/pinentry-gtk > > > > > > to gpg-agent.conf. Replace gtk by qt or gtk2 according on your taste. > > > Also try to run pinnetry using exactly the filename as given in that > > > line. > > > > The pinentry is not the issue, I configured it in gpg-agent.conf and it > > is found. I looked a bit deeper and apparently someone is talking garbage > > to the gpg-agent program. Following is from the agent's debug log: > > > > ... > > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > display=:0.0 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > lc-ctype=en_US.UTF-8 > > 5 - 2005-06-02 15:46:43 gpgsm[7635.0x807d230] DBG: <- OPTION > > lc-messages=en_US.UTF-8 > > > > That are the options the agent supposedly gets. BUT, somebody is lying > > here! Because this is what I can see if I strace the agent: > > > > 19760 read(0, "OPTION display=:0.0", 1002) = 19 > > 19760 read(0, "OPTION lc-ctype=en_US.UTF-8", 1002) = 27 > > 19760 read(0, "OPTION display=en_US.UTF-8", 1002) = 26 > > > > So, the first and second option are correct but the third one is garbage. > > The debug output says it's "lc-ctype=en_US.UTF8" but what the agent gets > > is "display=en_US.UTF8" which is completely bogus. And as a result > > pinentry fails to open the display. Now the question is where does that > > bogus option come from? Is it kmail which is talking to gpg-agent > > directly or is gpgme involved? I have no idea how the chain of command > > works in kmail from KDE 3.4.1. > > Forget that last sentence, it's of course gpgsm which is screwing things up > here. SUSE ships version 1.9.14. I'll have a look at it and see why it's > talking garbage to the agent. > > O.k., I keep following up to myself. Looks like gnupg-1.9.14 has a "brown paper bag" bug in common/asshelp.c ;-). It's fixed in 1.9.15, SUSE apparently shipped a broken version of gpg2 in 9.3. Karsten. -- "Not Hercules could have knock'd out his brains, for he had none." -- Shakespeare _______________________________________________ Gpa-dev mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gpa-dev
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) iD8DBQBCn4Q+6/OfRf0i9j8RAtMTAKCfov2OnMrF32arkUfTRIDNVbjmqQCguwBy 61zGLTqLKImNPuRQyQB5LI0= =A2rO -----END PGP SIGNATURE-----