From: Daiki Ueno <ueno@gnu.org>
To: ding@gnus.org
Subject: RFC: use NSS for S/MIME
Date: Thu, 03 Mar 2016 17:20:33 +0900 [thread overview]
Message-ID: <m3io14km5q.fsf-ueno@gnu.org> (raw)
Hello,
After seeing Greg's report on S/MIME interoperability issue[1], I was
thinking that it might be a good idea to add an S/MIME backend using NSS
instead of gpgsm.
The rationale behind this are:
- The certificate/key database could be shared with other major MUAs,
such as Evolution or Thunderbird.
- For OpenPGP, GnuPG is the de-facto and there is no free alternative.
For S/MIME, however, NSS is more widely used, and I expect that it had
been tested better.
What do people think? I have a basic wrapper implementation[2] (though
I might not have time to finish the integration of it into Gnus).
Regards,
Footnotes:
[1] http://article.gmane.org/gmane.emacs.gnus.general/86677
[2] https://github.com/ueno/smime-nss-el
--
Daiki Ueno
next reply other threads:[~2016-03-03 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 8:20 Daiki Ueno [this message]
2016-03-04 14:52 ` Jens Lechtenboerger
2016-03-04 22:38 ` Daiki Ueno
2016-03-06 14:58 ` Jens Lechtenboerger
2016-03-23 18:50 ` 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=m3io14km5q.fsf-ueno@gnu.org \
--to=ueno@gnu.org \
--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).