From: David Engster <deng@randomsample.de>
To: "Jose A. Ortega Ruiz" <jao@gnu.org>
Cc: ding@gnus.org
Subject: Re: problems with smime signatures
Date: Sat, 16 Jun 2012 17:03:22 +0200 [thread overview]
Message-ID: <871ulf8fk5.fsf@randomsample.de> (raw)
In-Reply-To: <87ehpmlxks.fsf@gnu.org> (Jose A. Ortega Ruiz's message of "Sun, 10 Jun 2012 22:29:55 +0200")
Jose A. Ortega Ruiz writes:
> I'm using Gnus v5.13 with the latest emacs snapshot (updated today), and
> i'm having trouble trying to sign using smime. I just use C-c C-m s s,
> which adds the signing cooking <#secure method=smime mode=sign> all
> right. I've configured smime following the instructions in the manual,
> which are basically the same as those in the emacs wiki
> (http://www.emacswiki.org/emacs/GnusSMIME), pointing Gnus to a valid (as
> far as i can tell) key file.
I've written that Wiki page a long time ago. Rather than using openssl,
you should try to use the gpgsm back end, as described here
http://thread.gmane.org/gmane.emacs.gnus.general/67372/focus=67400
-David
prev parent reply other threads:[~2012-06-16 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 20:29 Jose A. Ortega Ruiz
2012-06-16 15:03 ` David Engster [this message]
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=871ulf8fk5.fsf@randomsample.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=jao@gnu.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).