Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: gpgsm for S/MIME (was Re: Bug#6654)
Date: Wed, 28 Jul 2010 07:35:46 +0200	[thread overview]
Message-ID: <87zkxcb231.fsf_-_@randomsample.de> (raw)
In-Reply-To: <84tynk4c8f.fsf@davestoy.home> (Dave Goldberg's message of "Tue, 27 Jul 2010 21:38:24 -0400")

Dave Goldberg writes:
> I'll have to try that patch as decrypting and viewing is nearly as
> important to me as being able to encrypt :-) If not, do the back ends
> allow one to use gpgsm for sending and the old openssl mode for
> reading?

Yes. Actually, that's what currently happening for decrypting S/MIME, so
if you've already got through the tedious openssl setup, you should be
fine.

The main advantage of gpgsm is that is has adopted the GPG-style key
management for certificates, so it's pretty straightforward to use. If
you verify a signed mail, you'll automatically have the sender's
certificate for future use. With openssl, I used a pretty lengthy code
snippet to snarf the certificate, save it and put a link to it in the
BBDB.

Also, the gpg-agent will take care of securely asking for passwords and
caching (although this can be a disadvantage if you're working on the
console; it is not always clear on which tty the dialog will pop up, but
you can always "seed" the agent with the password beforehand).

-David



      reply	other threads:[~2010-07-28  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 22:10 Bug#6654 Dave Goldberg
2010-07-27  4:19 ` Bug#6654 Daiki Ueno
2010-07-27  7:26   ` Bug#6654 David Engster
2010-07-28  1:38     ` Bug#6654 Dave Goldberg
2010-07-28  5:35       ` 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=87zkxcb231.fsf_-_@randomsample.de \
    --to=deng@randomsample.de \
    --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).