From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject:
Date: Sun, 16 Aug 2015 19:41:08 +0200 [thread overview]
Message-ID: <1439746876-23654-1-git-send-email-david@tethera.net> (raw)
In-Reply-To: <54CA467B.30408@gnome.org>
It turns out S/MIME encryption requires non-trivial additional code in libgmime. There is no reason to wait for that to support signtures (via emacs+openssl|epg), and verification (via notmuch-cli).
Here we also test encryption, relying on emacs message-mode facilities.
(At least) two things could be improved here:
- we are using some unholy mix of openssl and gpgsm, and it would
probably be best to get everything working with gpgsm, since
we are already working with gpg and gpg-agent.
- It should be possible to do S/MIME decryption on the emacs level using e.g. smime-decrype-region.
On the other hand, it seems like supporting signature verification
is a step forward.
next prev parent reply other threads:[~2015-08-16 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 12:42 gmime and S/MIME David Bremner
2015-01-29 14:40 ` [gmime-devel] " Jeffrey Stedfast
2015-08-16 17:41 ` David Bremner [this message]
2015-08-16 17:41 ` [PATCH 1/8] crypto: refactor context creation to facilitate further work David Bremner
2015-08-16 17:41 ` [PATCH 2/8] crypto: make crypto ctx initialization an array David Bremner
2015-08-16 17:41 ` [PATCH 3/8] cli: let the user know which protocol is unknown or unsupported David Bremner
2015-08-16 17:41 ` [PATCH 4/8] test: initial tests for S/MIME and notmuch-emacs David Bremner
2015-08-16 17:41 ` [PATCH 5/8] test: add broken S/MIME signature verification test for notmuch CLI David Bremner
2015-08-16 17:41 ` [PATCH 6/8] cli: crypto: S/MIME verification support David Bremner
2015-09-26 11:58 ` Jani Nikula
2015-08-16 17:41 ` [PATCH 7/8] debian: Recommend gpgsm for S/MIME support David Bremner
2015-08-16 17:41 ` [PATCH 8/8] debian: add gpgsm as build dependency David Bremner
2015-09-26 17:32 ` Daniel Kahn Gillmor
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439746876-23654-1-git-send-email-david@tethera.net \
--to=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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 read-only IMAP folder(s) and NNTP newsgroup(s).