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

Marck,

> Only encrypted signed messages will result in a decrypted version.

  Ah, so it does. I was keying CTRL-SHIFT-D for signed messages,
  instead of CTRL-SHIFT-C.

> If it were decrypted in-line then you really would lose that
> opportunity since the original message would be replaced with the
> decrypted version.

  By "in-line" what I was really trying to say is "on-the-fly" - TB!
  should always store the message as it was received. So if I received
  a signed message and want it displayed in the viewer TB! would do
  it's best to check the signature automatically. Similarly with
  encrypted messages, if I have a cached passphrase in PGP then there
  is nothing to stop TB! decrypting the message for me when I open it in
the
  viewer. There should, of course, always be a way to view the message
  as it was originally transmitted if you are interested in that. For
  me it's the manual intervention on every message that is signed or
  encrypted that makes it feel less integrated.

> BTW, if unattended security is of concern to you then you should
> seriously consider using SecureBat!

  It's not a major concern for me, just an example of why I'm not so
  keen on the decrypted copies of messages. If TB! was decrypting as
  it went the PGP passphrase caching would alleviate this problem to
  some degree.

  Thanks for your response, I will give that example Read filter a
  try.

  Regards,

  Graeme.

- --
Graeme J Hosking
[EMAIL PROTECTED]

http://www.hosking-online.com/

-----BEGIN PGP SIGNATURE-----
Version: 6.5.8ckt http://www.ipgpp.com/
Comment: KeyID: 0xCA4E46C2

iQA/AwUBPhQizWG9Y2LKTkbCEQIKPwCg+U7/k8df/Tbla6CcLyVjwEoulcMAoKzs
/mHBcxXsjXJ0Qw9cVIJh2J4h
=WFf9
-----END PGP SIGNATURE-----



________________________________________________
Current version is 1.62 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to