From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: S/MIME
Date: 05 Nov 2000 00:43:16 -0500 [thread overview]
Message-ID: <2n4s1n3rez.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <ilu66m39ne8.fsf@barbar.josefsson.org>
Simon Josefsson <sj@extundo.com> writes:
> Bruce Stephens <bruce+gnus@cenderis.demon.co.uk> writes:
>
> > How do I verify signatures? I just get the error that
> > application/x-pkcs7-signed (or something like that) is unknown?
>
> S/MIME signature verification should work now. Unfortunately S/MIME
> doesn't use multipart/encrypted (rfc 2015), so there's a little more
> work involved getting decryption to work too. Shouldn't take too long
> though.
Two possible problems:
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?
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.
ShengHuo
next prev parent reply other threads:[~2000-11-05 5:43 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 ` ShengHuo ZHU [this message]
2000-11-05 12:18 ` S/MIME Simon Josefsson
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=2n4s1n3rez.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).