From: Simon Josefsson <sj@extundo.com>
Cc: ding@gnus.org
Subject: Re: S/MIME
Date: 05 Nov 2000 13:18:50 +0100 [thread overview]
Message-ID: <ilur94q1uj9.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <2n4s1n3rez.fsf@tiger.jia.vnet>
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> 1. The output of openssl may contain ^M's. At least, I found one at
> the end of the first MIME boundary. I don't know why. Should those
> ^M's be removed?
OpenSSL problem, fixed in 0.9.6. I believe the signature isn't
calculated over the boundary so this shouldn't cause any problems, I
think.
> 2. When smime-verify-buffer is called, the article headers have been
> decoded, which means that users may have to pick a coding system to
> encode those non-ASCII characters before it is sent to openssl. It
> would be better to copy the article to a new buffer, and remove
> unnecessary headers, or just narrow to the article body.
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?
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.
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.
next prev parent reply other threads:[~2000-11-05 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 22:38 S/MIME Bruce Stephens
2000-11-04 14:23 ` S/MIME ShengHuo ZHU
2000-11-05 2:13 ` S/MIME Simon Josefsson
2000-11-05 5:43 ` S/MIME ShengHuo ZHU
2000-11-05 12:18 ` Simon Josefsson [this message]
2000-11-05 13:36 ` S/MIME ShengHuo ZHU
2000-11-05 14:14 ` S/MIME Simon Josefsson
2000-11-28 0:08 ` S/MIME suggestions Bruce Stephens
2000-11-29 21:22 ` Simon Josefsson
2000-11-30 0:34 ` Bruce Stephens
2000-11-30 9:54 ` Simon Josefsson
2000-11-30 1:25 ` ShengHuo ZHU
2000-11-30 2:00 ` Kai Großjohann
2000-11-30 9:36 ` Simon Josefsson
2001-01-15 17:09 ` Simon Josefsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilur94q1uj9.fsf@barbar.josefsson.org \
--to=sj@extundo.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).