Re: MIME Security with PGP (RFC2015)

[Raja R Harinath <harinath@cs.umn.edu>]

Simon Josefsson <simon@josefsson.org> writes:
> Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> 
> > If we implemented both protocols, I think we should rename it to
> > rfc1847.el instead of rfc2015.el.
> 
> Yes.  I'm writing rfc1847.el now, with S/MIME support.
> (PGP/MIME should be easy given yours and Florians work.)
> 
> I think I'm going to take a different approach than you and Florian.
> Instead of adding MML tags that say that a part should be
> signed/encrypted when sending it, I'm adding commands for "sign this
> MML part" and "encrypt this MML part" that does the signing
> immediately.
[snip] 
> I would like this better than encrypt-when-send, with it I would
> always have the feeling that I never knew what was sent.

How do you ensure that if the signature still matches?  I could create
a part, sign it, edit it some more, and forget to request a recompute
the signature.  Will it flag an error when the message is attempted to
be sent?  What does the user have to do to fix the error?

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash