Re: MIME Security with PGP (RFC2015)

[Simon Josefsson <simon@josefsson.org>]

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.

So if you are editing a MML article like

<$multipart type=mixed>
<$part>
Hi there
<$part>
Hi again
<$/multipart>

and call the "sign part" function on the <$multipart> tag and select
S/MIME signing, you'd end up with

<$multipart type=signed>
<$multipart type=mixed>
<$part>
Hi there
<$part>
Hi again
<$/multipart>
<$part type=application/x-pkcs7-signature buffer=*signature* raw=t>
<$/multipart>

or possibly

<$multipart type=signed>
<$part type=multipart/mixed buffer=*whatever* raw=t>
<$part type=application/x-pkcs7-signature buffer=*signature* raw=t>
<$/multipart>

in the buffer.

I would like this better than encrypt-when-send, with it I would
always have the feeling that I never knew what was sent.

What do you think?