-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On April 22, 2001, at 6:34:04 AM, Maxim Masiutin wrote:

MM>  This beta now supports GnuPG.

Everything seems to work fine considering it's the first attempt to
support GPG, except that I receive a Program warning and error messages
when attempting to encrypt data. Warning message example:

gpg: using secondary key 595A9A4F instead of primary key 7BA3FDCE

I am not sure what "key 595A9A4F" that is, but I'm presuming it's my
Subkey, as that is what is used for encryption. Why then would the Plugin
issue a warning message about it's use?

Other times, the Plugin will cause an error message because it cannot find
the Public Key when the Public Key is actually present:

gpg: using secondary key 595A9A4F instead of primary key 7BA3FDCE
gpg: Graham <[EMAIL PROTECTED]>: skipped: public key not found
gpg: [stdin]: encryption failed: public key not found

The problem here though has to do with how the To: line is addressed. In
the above example, "Graham" does not equate to "Graham Todd" as it's
expressed on the actual User ID. If I simply edit the To: line so that it
reads "Graham Todd <[EMAIL PROTECTED]> and matches the User ID,
then the encryption proceeds without incident, except for the same warning
message as before:

gpg: using secondary key 595A9A4F instead of primary key 7BA3FDCE



Nick

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     -=N.J. Andriash  |  Vancouver, B.C. Canada=-
  PGP-Basics List Moderator | PGP Key ID: 0x7BA3FDCE
GnuPG v1.0.4-2 (MingW32) | TB! v1.52 Beta 11 | Win98 SE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4-2 (MingW32)
Comment: Join PGP-Basics: [EMAIL PROTECTED]

iD8DBQE646aDxQKEdHuj/c4RAgXqAKD7FlAuaiWotaJ2GQ4rBLGaPUDGQgCg2FX4
oFG5IlAMKlXu1dK/+DS6dPY=
=GFmP
-----END PGP SIGNATURE-----

-- 
______________________________________________________
Archives   : <http://tbbeta.thebat.dutaint.com>
Moderators : <mailto:[EMAIL PROTECTED]>
Unsubscribe: <mailto:[EMAIL PROTECTED]>

You are subscribed as : [email protected]


Reply via email to