-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi [EMAIL PROTECTED],
@7-Jan-2003, 13:30 +0100 (12:30 UK time) [EMAIL PROTECTED] [C] in [EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said: MDP>> Like most windows MUAs The Bat! does not implement PGP/MIME in MDP>> any of the supported PGP/GnuPG profiles. That's what you're MDP>> actually talking about. This does not answer the original MDP>> question. C> Well, ok, a bit emotional, but that's because ritlabs doesn't C> feel like replying to questions about the PGP/GnuPG plug-in. RITlabs don't actually reply to many questions, period. They don't have many staff and are working very hard on new releases. Also, it is the Christmas / New year holidays in Moldova yesterday and today so the offices are closed. C> It did cost me a whole day to find out why I couldn't decrypt the C> messages people sent me with TheBat, and just to find out that C> TheBat is using a so called "not very secure, old standard" C> (these are not my words! You'll find them on the OpenPGP C> website!) for message encoding. The words are misleading. This "old standard" is widely used and is absolutely "standard". The PGP/MIME is gradually spreading but is not widely used/accepted. Especially not in Windows software. C> It is FACT that TheBat won't encrypt attached files/documents! Not using PGP/MIME it won't. It will using S/MIME, which *is* a widely used and ratified standard in all senses. All implementations of S/MIME should inter-operate in ways that PGP/MIME implementations don't yet seem to. C> This is not exactly what I expected. That's because you have been misled by a Linux MUA user group that thinks that the development trend Evolution has taken over the past six months (of full support for PGP/MIME) is suddenly the only game in town. It isn't. C> And it also doesn't decrypt attached files in received mails. So C> there IS incompatibility with other mailers! Only those using the not-very-widely used PGP/MIME "standard". C> When I receive a mail from somebody else, who encrypted it using C> GnuPG (same version) and I can not decrypt it without other, C> additional tools, there is an incompatibility issue, no matter C> why. Of course it matters "why". If the standard is not yet widespread in implementation then you should be made aware of that. If someone is sending you encrypted data then they should do so in a compatible manner and in a way that *you* can decrypt it. You should be aware of the limitations of the standards themselves and the ways in which OpenPGP is used and implemented. Perhaps they should even have used x509 S/MIME to do it if it was that important that the attachment required encryption. The TB programmers have a long stated aim to support PGP/MIME but there hasn't been consensus about how the standard should be implemented until more recently. As I see it, the programmers at RITlabs are currently engaged in other development tasks, particularly the rapidly approaching v2, and may not have the time available right now to implement the "new" PGP standard. - -- Cheers -- .\\arck D Pearlstone -- List moderator TB! v1.63 Beta/2 on Windows 2000 5.0.2195 Service Pack 2 ' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1rc1-nr1 (Windows 2000) iD8DBQE+Gs/2OeQkq5KdzaARAlIcAKDGXgzZ3YY3j8zUg985rD7khtdnKQCfQakk ITX71SvPPmXVsOhz+50KfcQ= =MYT4 -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
