Sun Jul 20 22:10:03 2003
[The correct mailing list for this is firstname.lastname@example.org. So please send=20
followups only to this address.]
On Saturday 19 July 2003 01:08, John Aldrich wrote:
> I *know* what I set the passphrase to on my PGP keys, but after
> upgrading to the "new and improved" GPG-Plugin, I can no longer use
> my GPG keys. It keeps telling me that I don't have a passphrase
> entered and automatically tries to send encrypted/signed emails, EVEN
> T HOUGH I DO NOT HAVE "AUTO-SIGN" ENABLED!
Did you properly configure the plugins? About the passphrase problem:=20
Please use pinentry-gtk if pinentry-qt doesn't work for you (which=20
seems to be the case). Please run to following command in a terminal=20
where you started gpg-agent resp. where the GPG_AGENT_INFO environment=20
variable is known:
echo Test | gpg --clearsign
Does this work?
BTW, you are obviously using KMail 1.5. Please update to KMail 1.5.2=20
> What the heck is the problem here, people? I manually compiled
> everything from the tarballs using the command-line options specified
> on the KMail site and have got the Daemon running, so why does it 1)
> refuse to recognize my passphrase
Did you actually get a chance to enter your passphrase? This is not=20
clear to me. If your passphrase contains non-ASCII characters then this=20
might be a reason.
> and 2) always assume I want to sign=20
> and/or encrypt my emails when I have it set to NOT sign/encrypt by
Again, please check the configuration of the _plugin_. Most of the=20
settings on the OpenPGP page only affect the built-in OpenPGP support.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc1 (GNU/Linux)
-----END PGP SIGNATURE-----