-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Marck,
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 C>> other mailers. The actual encoding standard uses encrypted C>> attachments, TheBat can en-/decrypt only the message itself. MDP> If you are going to answer questions on a public forum, please try MDP> to be more accurate than emotional. This is entirely incorrect in MDP> every respect. MDP> Like most windows MUAs The Bat! does not implement PGP/MIME in any MDP> of the supported PGP/GnuPG profiles. That's what you're actually MDP> talking about. This does not answer the original question. Well, ok, a bit emotional, but that's because ritlabs doesn't feel like replying to questions about the PGP/GnuPG plug-in. It did cost me a whole day to find out why I couldn't decrypt the messages people sent me with TheBat, and just to find out that TheBat is using a so called "not very secure, old standard" (these are not my words! You'll find them on the OpenPGP website!) for message encoding. It is FACT that TheBat won't encrypt attached files/documents! This is not exactly what I expected. And it also doesn't decrypt attached files in received mails. So there IS incompatibility with other mailers! When I receive a mail from somebody else, who encrypted it using GnuPG (same version) and I can not decrypt it without other, additional tools, there is an incompatibility issue, no matter why. Best regards, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) iD8DBQE+GshKYTfQI7+Ck0ARAqA+AJwKepJPgUD5aPmkr+sjcnSz2UIEywCgjv5H X4SUQtvZ404JmET8cC7dWLQ= =Php2 -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
