From: Simon Josefsson <sj@extundo.com>
Cc: ding@gnus.org
Subject: Re: S/MIME suggestions
Date: 30 Nov 2000 10:54:09 +0100 [thread overview]
Message-ID: <ilun1eh7pku.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <878zq2mh6t.fsf@cenderis.demon.co.uk>
Bruce Stephens <bruce+gnus@cenderis.demon.co.uk> writes:
> Yes, probably. The way Outlook Express does it (by default) is a bit
> OTT, but it expresses the various possibilities. When you open a
> signed and/or encrypted message, you get a screen with a number of
> items on it, with ticks or crosses by them. I forget exactly the
> list, but it'll include things like "signature verifies", "certificate
> trusted", "certificate issuer trusted", "certificate subject matches
> from address", and so on. (Things for expiry, too, I guess.)
That's too obtrusive imho, but there should be a menu or something on
the security button so one could list all details of a signed part.
> Anyway, this is making real progress---S/MIME support seems to be
> approaching PGP's in usability.
Deciphering S/MIME messages doesn't work though. Mainly because
S/MIME didn't use RFC 1847. Sigh. I have a sort-of working elisp
ASN.1 library now, that is able to parse those PKCS#7 blobs and find
out what they are. I'll check it in soon..
next prev parent reply other threads:[~2000-11-30 9:54 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 ` 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 [this message]
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=ilun1eh7pku.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).