Hi Oliver,
on 11 Apr 99 15:55:17 +0200, You wrote:
> > Depends. Are they free, or do I need a credit card number. In the latter case,
> > could you also mail me Ingos credit card details? ;-)
>
> No problem, but his visa statement suggests he already exceeded
> his credit limit.
No wonder, "he" registered some thousand copies of vapor products
today, eh Olli? ;-))
To get on topic again, let me repeat some of my suggestions and
questions regarding the pgp support while you're reading anyway... ;)
Those features are how I would define (nearly) perfect pgp
integration, being realistic I don't expect them in the next few
versions - non the less, please look at them and consider putting them
on your todo list.
--8<---
What is "Clearsign" meant for? With the default commands, it only
omits the b (causing a signature separate from the message). If it was
meant for clearsigning in the sense PGP refers to this, "pgp -z %p
-sat +clearsig=on %f -o %o" would be the correct command?!
Checking of signatures of mails doesn't seem to be supported?
A message with an application/pgp-signature attachment is treated
like a normal message and "PGP decrypt" leads to pgp asking for the
file belonging to the signature - MD-II should pass the message name
here.
The handling of the messages should be more automated, ie. the
application/pgp-encrypted attachment just containing the version
shouldn't be displayed in the main message reader window,
application/pgp-signature or the actual data (only if it's ASCII
armored) should be displayed like normal text-attachments.
When using "PGP decrypt", only the decrypted part of the mail gets
displayed resulting in the mail body being interpreted as header lines
and being displayed in the header color (default blue).
It would be better if the whole mail with headers etc. would be
displayed and the decrypted mail body would be inserted.
There should be a prefs option to keep (cache) the decrypted message
during a session (so that closing the reader and opening it again
doesn't cause the encrypted message being displayed again, requiring
pgp to be launched again - slow even on a 060 - my PPC version isn't
much faster either...
But of course, messages encrypted with the -m ("for your eyes only")
option of pgp shouldn't be cached. There should be another option to
automatically decrypt all encrypted messages (maybe showing some key
or lock icon in the reader window to show that the message was
encrypted).
Signatures should be checked automatically too (maybe another icon
showing that the message was signed) and instead of displaying "This
part of the message does not contain text." along with the save and
view gadgets for the application/pgp-signature attachment, it should
display the important lines of the pgp output in that place, ie. "Good
signature from user ... . Signature made ... with key ...". A warning
requester should pop up for invalid signatures, and an optional(!)
"get required key from keyserver" requester if PGP 5.x is used and the
key that made the signature isn't in the pubring.
The reader window should have a "save unencrypted" button that allows
to save the unencrypted message, ie. replace the encrypted one with
the unencrypted one in MD-II's database for those non-confidential
messages that were just encrypted "for fun".
The "Copy self" option should be extended to a cycle gadget allowing
either "No copy", "Copy encrypted", "Copy unencrypted" or "Copy
encrypted to self".
�SPOOL would always get the copy encrypted to the other user, the
apropriate �PRIV folder would get either no copy at all ("No copy"),
the same as �SPOOL ("Copy encrypted" ), an (unencrypted) copy of the
message ("Copy unencrypted") for the just encrypted "for fun" messages
or a copy that has been encrypted to this user ("Copy encrypted to
self"), ie. one that is only readable with the passphrase.
Keeping the message encrypted to the other user is only useful for
resending it, otherwise it's of no use as only the other user can
decrypt and read it, so the other options would be very useful, esp.
the last option as one would later be able to read what one has
written to the other user, but it's still kept encrypted on disk
(and automatically (if autodecrypt option is enabled) decrypted by
MD-II as described above).
The "Copy unencrypted" state would automatically reset to the status
set before after the message is sent (so that the next message won't
be saved unecrypted accidentally), the other states would be remebered
by MD-II (like "Copy self" now), the "Copy *" states would lead to a
normal copy when no encryption is used.
Maybe the addressbook should have options to automatically sign and/or
encrypt messages sent to the specific user.
elmar
--
// <[EMAIL PROTECTED]> ICQ: 13799187 Public PGP key available via pgp.net
// A4000T 68060-50 & 604e-233, 2+144MB, 9GB, SyJet 1.5GB, Cybervision64/3D,
\\// Member of Team *AMIGA* Crack RC5 now! Prelude, Ariadne, Eizo T57S 17"
