From: David Bremner <david@tethera.net>
To: Neale Pickett <neale@lanl.gov>, notmuch@notmuchmail.org
Subject: Re: State of S/MIME support (emacs)
Date: Thu, 01 Sep 2016 17:39:03 -0300 [thread overview]
Message-ID: <87zinr4aoo.fsf@tesseract.cs.unb.ca> (raw)
In-Reply-To: <87poons9fs.fsf@lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Neale Pickett <neale@lanl.gov> writes:
> I just set up notmuch an hour ago and it seems like exactly what I need
> to better perform my project management job. Except I get a lot of
> S/MIME stuff.
>
> Web searching tells me there have been various attempts for S/MIME
> support. Before I dive into code, I thought I should ask if anybody else
> has been playing around with S/MIME, either in the command-line tools or
> in the emacs client. Specifically, I need to be able to decrypt S/MIME
> encrypted email.
>
> I'll refrain from expounding on how I *feel* about needing S/MIME.
The wall I hit when I was working on it was that libgmime does not
(correctly) support S/MIME encryption/decryption. So that's why the
command line tools only support signature verification and not
decryption. The "good of humanity" solution (assuming you don't think
that is eradication of S/MIME) would be to add this support to
libgmime. I think upstream would take the patches, but didn't sound like
it was likely to happen without external contribution. The "dirty hack"
solution would be to use gpgsm or openssl directly from emacs.
d
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 647 bytes --]
next prev parent reply other threads:[~2016-09-01 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 19:32 State of S/MIME support (emacs) Neale Pickett
2016-09-01 20:39 ` David Bremner [this message]
2016-09-01 22:36 ` Neale Pickett
2016-09-01 21:16 ` 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=87zinr4aoo.fsf@tesseract.cs.unb.ca \
--to=david@tethera.net \
--cc=neale@lanl.gov \
--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).