-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Allie,
C>> the "TB" implementation of GnuPG is something close to crap! They C>> based it on old an insecure encoding standards, what makes it C>> impossible for TheBat to decrypt GnuPG encrypted messages from other C>> mailers. The actual encoding standard uses encrypted attachments, C>> TheBat can en-/decrypt only the message itself. AM> I've been using GnuPG with TB! for a long time. With the plug-in you can AM> sign, decrypt and encrypt messages. However, it uses a strict UID AM> matching system (smart matching) when doing so in that it will select a AM> key to use only if the key has an exactly matching name <address> AM> combination to the one the plug-in is looking for. Key management and AM> GnuPG configuration, you have to do via the CLI or you install either AM> GPGShell or WinPT for this. Well, just try to have some one send you an encrypted mail with evolution or so. You'll find yourself unable to decrypt it with TheBat. Sure, you can use GPshell, but that's not what I understand if ritlabs says they have a plugin for GnuPG. The new message encoding standards can only be decrypted with additional tools like GPshell or by command line with gpg. - -- Best regards, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) iD8DBQE+GsT4YTfQI7+Ck0ARAhU6AKCHGi0pibgcCfQYC9qepkP+u2nuJgCfQMLq TlN3gYHmJFXrj7BCCEa/Wqk= =X6eH -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html