Re: S/MIME

[ShengHuo ZHU <zsh@cs.rochester.edu>]

Simon Josefsson <sj@extundo.com> writes:

> Right.  I added mm-handle-multipart-* to get information of a MIME
> multipart, and it's used by mml-smime-verify now.  What do you think,
> is the copying too costly?

What kind of information mml-smime-verify needs? CTL, From and To?

> I think the proper solution would be to add a reference to the "upper"
> MIME object within a MIME handle.  I'm not sure how to do that in
> elisp though.  The uppermost MIME handle should also include a
> reference to the RFC822 article headers too, because the "From:" line
> should be verified to match the certificate used to sign a message.

"From:" line could be saved in a dynamic variable when
mm-dissect-buffer is called without no-strict-mime, like what I did in
PGP/MIME encryption.

> Also, what should happen when verification fails?  For S/MIME it print
> a message saying if the verification was successful or not, PGP/MIME
> doesn't seem to print anything, and display a *MML2015* buffer if the
> verification fail.  Neither is very intuitive if you got 100 signed
> parts in a mail.  I think it would be nice if verification/decryption
> status was displayed such as

> [text/plain; signed (S/MIME): Undecided]
> [text/plain; signed (S/MIME): OK]
> [text/plain; signed (S/MIME): Failed]
> 
> and you could pop up the menu and get some kind of "Security info" for
> that MIME part, with more details.

It sounds good to me.  I suggest to forge attributes `gnus-info' and
`gnus-details' in content-disposition.

ShengHuo