From: Bruce Stephens <bruce+gnus@cenderis.demon.co.uk>
Subject: S/MIME suggestions
Date: 28 Nov 2000 00:08:02 +0000 [thread overview]
Message-ID: <871yvxdkm5.fsf_-_@cenderis.demon.co.uk> (raw)
In-Reply-To: <ilu66m39ne8.fsf@barbar.josefsson.org>
Just a couple of suggestions for signed email mostly. Most user
agents don't *require* that certificates verify (i.e., you don't
*have* to have the issuer's certificate). They complain loudly if the
certificate doesn't validate, obviously, but they allow you to trust a
specific certificate, without having to trust all certificates signed
by a particular issuer.
Openssl allows this using the -noverify flag. So (in a pleasantly
contradictory fashion), "openssl smime -verify -noverify ..." makes
perfect sense.
Also, "openssl smime -verify ... -signer <file>" extracts the
certificate (presuming there is one). That strikes me as a very
convenient feature to use. Especially considering that "openssl x509
-email -noout -in <cert>.pem" prints out a list of email addresses for
the given certificate, which would presumably allow Gnus to check that
the email addresses match with the From header.
next prev parent reply other threads:[~2000-11-28 0:08 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 ` Bruce Stephens [this message]
2000-11-29 21:22 ` S/MIME suggestions 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=871yvxdkm5.fsf_-_@cenderis.demon.co.uk \
--to=bruce+gnus@cenderis.demon.co.uk \
/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).