Re: kmail openpgp plugin problems [FIXED]
Whats needed is for the GPG_AGENT_INFO environment variable to be set. As i was loading gpg-agent with a shell script nothing else was seeing this variable. The only way i can start gpg-agent properly is to put it into my /usr/bin/startkde script. Its in my xsession but that doesnt do anything, how are .xsession files supposed to work? Tom
Re: kmail openpgp plugin problems
On Saturday 18 Jan 2003 10:14 pm, Hendrik Sattler wrote: > Am Samstag, 18. Januar 2003 22:30 schrieb Tom Badran: > > Ok, i now have your versions of the above package and all the packages in > > the aegyption directory on ktown, and rebooted to make sure i get new > > clean gpg-agent etc running. I still get exactly the same errors about > > not having a passphrase. > > Question: Your private key DOES have a passphrase, doesn't it? You might > take a look at the goals of the aegypten project and thus keys without a > passphrase might not be accepted. Yes it does. Tom
Re: kmail openpgp plugin problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 18 Jan 2003 11:00 pm, Dirk Schmidt wrote: ... > I've experienced exactly the same problem. > But, after I installed mutts-gpgme and libncursesw5 (which will be > installed automatically by apt-get), the pinentry dialog appeared when > using mutts. The strange thing is, that thereafter pinentry-gtk worked from > kmail, too. > > I could not proove until now, that the installation of the packages above > was the real "solution", though I didn't change anything apart from that. > > Maybe you could also try your luck with installing mutts-gpgme and create a > signed message with it. > > If the problem disappears on your system too, my observation would be > confirmed and we then could search the problem's real cause. Not less > strange is the fact, that you can remove mutts-gpgme and libncursesw5 then > and kmail will still work. I don't know what I am talking about ... but, If the mutts-gpgme use creates a .xxx file in your home directory which pinentry-gtk needs to work then the behaviour that you see will be explained. perhaps an ls -al on $HOME to see of there are any candidates that were created about the time of first use might be a start. - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+KnCVuFHxcV2FFoIRAouiAKC2BE4yhL7uRPckfLJmDNoeh+QL5QCgtbjC M91Mhg+/bdJT+PQgkYivPzI= =Poun -END PGP SIGNATURE-
Re: kmail openpgp plugin problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 18. Januar 2003 22:30 schrieb Tom Badran: > On Saturday 18 Jan 2003 8:27 pm, Ralf Nolden wrote: > > > This message could not be signed! > > > The Crypto Plug-In '/usr/lib/cryptplug/gpgme-openpgp.so' reported the > > > following details: #19 : No Passphrase [...] > > I've updated the packages again due to that Matze found out that > > apparently it doesn't work with libgcrypt-1.1.11 but requires 1.1.10. > > Also please make sure that you *don't* use any of the original packages > > from unstable in conjunction with the aegypten stuff, but my packages. > > That makes it easier to track down any problems. Especially those are: > > > > libgcrypt > > cryptplug > > gpgme > Ok, i now have your versions of the above package and all the packages in > the aegyption directory on ktown, and rebooted to make sure i get new clean > gpg-agent etc running. I still get exactly the same errors about not having > a passphrase. > > Any more ideas? I've experienced exactly the same problem. But, after I installed mutts-gpgme and libncursesw5 (which will be installed automatically by apt-get), the pinentry dialog appeared when using mutts. The strange thing is, that thereafter pinentry-gtk worked from kmail, too. I could not proove until now, that the installation of the packages above was the real "solution", though I didn't change anything apart from that. Maybe you could also try your luck with installing mutts-gpgme and create a signed message with it. If the problem disappears on your system too, my observation would be confirmed and we then could search the problem's real cause. Not less strange is the fact, that you can remove mutts-gpgme and libncursesw5 then and kmail will still work. Dirk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+KdyADtHLVOb9JRcRAlNaAJwOoCsuWeUDHQdJnFlxQUkGloV6ewCfQAFC xjg6dfbDuYcTxjKq6R3PV4E= =ScGc -END PGP SIGNATURE-
Re: kmail openpgp plugin problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 18. Januar 2003 22:30 schrieb Tom Badran: > Ok, i now have your versions of the above package and all the packages in > the aegyption directory on ktown, and rebooted to make sure i get new clean > gpg-agent etc running. I still get exactly the same errors about not having > a passphrase. Question: Your private key DOES have a passphrase, doesn't it? You might take a look at the goals of the aegypten project and thus keys without a passphrase might not be accepted. HS - -- Mein GPG-Key ist auf meiner Homepage verfügbar: http://www.hendrik-sattler.de oder über pgp.net PingoS - Linux-User helfen Schulen: http://www.pingos.schulnetz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE+KdHczvr6q9zCwcERAqcwAJ49WUkriksxr+2D0ERZ0GoBnHUsfwCeNTXs s45uvRLQ7SuDtKqGS0VB9Tw= =B4sW -END PGP SIGNATURE-
Re: kmail openpgp plugin problems
On Saturday 18 Jan 2003 8:27 pm, Ralf Nolden wrote: > I've updated the packages again due to that Matze found out that apparently > it doesn't work with libgcrypt-1.1.11 but requires 1.1.10. Also please make > sure that you *don't* use any of the original packages from unstable in > conjunction with the aegypten stuff, but my packages. That makes it easier > to track down any problems. Especially those are: > > libgcrypt > cryptplug > gpgme Ok, i now have your versions of the above package and all the packages in the aegyption directory on ktown, and rebooted to make sure i get new clean gpg-agent etc running. I still get exactly the same errors about not having a passphrase. Any more ideas? Would you like to see any of my configs/.gnupg directory structure? Tom
Re: kmail openpgp plugin problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Samstag, 18. Januar 2003 20:36, Tom Badran wrote: > Firstly, i set up everything exactly as the aegypten projects website > describes except using pinentry-gtk instead of qt as reccomended by ralf, > and btw im using ralfs debs. I also have been using the same gpg setup for > a long time without problems from the command line. > > Strange problem, i can encrypt emails fine, im not asked for a password and > all works well, to myself and to others. However i can sign messages, i get > a pop up box saying : > > This message could not be signed! > The Crypto Plug-In '/usr/lib/cryptplug/gpgme-openpgp.so' reported the > following details: > #19 : No Passphrase > Your configuration might be invalid or the Plug-In damaged. > Please contact your system administrator. > > Also, when recieving an encrypted message i get: > > Cannot decrypt message. > Error: No passphrase. > Content could *not* be decrypted. > reason: > Crypto Plug-In /usr/lib/cryptplug/gpgme-openpgp.so could not decrypt > the data. > proposal: > Error: No passphrase. > End of encrypted message > > Like i say, it works encrypting, but not decrypting or signing, and im > never asked for my passphrase. I am definately using the plugin and not the > inline version (i activated the plugin and in the new message dialog it now > defaults to "OpenPGP (plugin)". > > Any Ideas? Hi Tom, I've updated the packages again due to that Matze found out that apparently it doesn't work with libgcrypt-1.1.11 but requires 1.1.10. Also please make sure that you *don't* use any of the original packages from unstable in conjunction with the aegypten stuff, but my packages. That makes it easier to track down any problems. Especially those are: libgcrypt cryptplug gpgme Ralf > > Thanks > > Tom - -- We're not a company, we just produce better code at less costs. - Ralf Nolden [EMAIL PROTECTED] The K Desktop Environment The KDevelop Project http://www.kde.org http://www.kdevelop.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+KbiWu0nKi+w1Ky8RAu17AJ9h0INY9iBr4HmN79+gjrda5Ho2PQCffkGR bfH5iEbwCu0DHO1JqGD3SpU= =XLKW -END PGP SIGNATURE-
