From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: best approach to S/MIME?
Date: Fri, 15 Mar 2013 16:22:40 -0400 [thread overview]
Message-ID: <smua9q4qupb.fsf@linuxpal.mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
I am trying to get set up with S/MIME. I have no personal cert yet, but
I have imported a correspondent's key and CA cert and marked the CA
trusted. gpgsm on the command line will verify a message.
I read this:
http://www.emacswiki.org/emacs/GnusSMIME
and set: (setq mml-smime-use 'epg)
which seems to be the default these days if epg exists.
(I am using gnus from git master, via load-path, and emacs 23.4.1.)
But I still get "No CA configured" when displaying a message (which is
really a base-64 encoded s/mime signed message).
This is in smime-verify-region which is the openssl variant.
Can someone tell me what the best thing to do is for S/MIME? (I have
been happily using OpenPGP with epg for many years.)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2013-03-15 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 20:22 Greg Troxel [this message]
2013-03-16 0:47 ` James Cloos
2013-03-18 9:34 ` Daiki Ueno
2013-03-18 11:22 ` Greg Troxel
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=smua9q4qupb.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.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).