On Saturday, September 17, 2005 at 1:08:20 PM [GMT -0500], Mary Bull wrote:
> Thanks for trying to help. > As I wrote to Michael, I don't think I have found anyone yet to test > this behavior using the conditions under which it occurs for me. I confirm the behaviour. Ok? :) You're absolutely right about what happens. To reproduce, one MUST be using PGP/MIME. Even Villi may do so provided he has PGP/MIME enabled in the PGP editor options when doing the test. - Compose a test message - Go to the privace options and enable 'encrypt when completed' and 'PGP/MIME On'. - Put the message in the outbox. If you're signing the message as well, you'll be prompted for your passphrase. - Now, open the Outbox and *re-open* the message in the editor by double clicking on it. - What opens in the editor is just the envelope text: This is a PGP encrypted message. Click the security button to decrypt/verify it All of the original message text will not be there. So when you hit send, you'll be encrypting the envelope text for PGP/MIME encryption messages. You'll not actually be sending the message you originally wanted to. This doesn't happen with non PGP/MIME messages since there's no MIME structure for TB! to stumble over and have problems with on re-opening in the editor. I don't even know if it's just a vulnerability of PGP/MIME or a bug in TB!. -- -= Curtis =- The Bat! v3.61.05 Echo (Beta) System Specs: http://specs.aimlink.name PGPKey: http://rsakey.aimlink.name -=-=- If at first you don't succeed, work for Microsoft.
pgp9wqyqFaDx2.pgp
Description: PGP signature
________________________________________________________ Current beta is 3.61.05 (Echo) | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
