From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: [PATCH] NEWS: cleartext indexing
Date: Sun, 22 Oct 2017 11:36:34 -0400 [thread overview]
Message-ID: <20171022153634.14802-1-dkg@fifthhorseman.net> (raw)
give a short summary of cleartext indexing of encrypted e-mail
messages.
---
NEWS | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/NEWS b/NEWS
index c2ebb644..895b7627 100644
--- a/NEWS
+++ b/NEWS
@@ -11,6 +11,24 @@ Out-of-tree builds
has been dropped. The same can now be achieved more reliably using
out-of-tree builds.
+Encrypted Mail
+--------------
+
+Indexing cleartext of encrypted e-mails
+
+ It's now possible to include the cleartext of encrypted e-mails in
+ the notmuch index. This makes it possible to search your encrypted
+ e-mails with the same ease as searching cleartext. This can be done
+ on a per-message basis with the --try-decrypt argument to indexing
+ commands (new, insert, reindex), or by default by running "notmuch
+ config set index.try_decrypt true".
+
+ Note that the contents of the index are sufficient to roughly
+ reconstruct the cleartext of the message itself, so please ensure
+ that the notmuch index itself is adequately protected. DO NOT USE
+ this feature without considering the security of your index.
+
+
Notmuch 0.25.1 (2017-09-11)
===========================
--
2.14.2
next reply other threads:[~2017-10-22 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 15:36 Daniel Kahn Gillmor [this message]
2017-10-22 17:07 ` [PATCH] NEWS: cleartext indexing David Bremner
2017-10-22 18:53 ` [PATCH] NEWS: document notmuch reindex Daniel Kahn Gillmor
2017-12-24 14:07 ` David Bremner
2017-10-30 12:46 ` [PATCH] NEWS: cleartext indexing Antoine Beaupré
2017-10-30 15:47 ` Daniel Kahn Gillmor
2017-10-30 16:16 ` Antoine Beaupré
2017-11-01 2:13 ` Daniel Kahn Gillmor
2017-11-23 14:21 ` Antoine Beaupré
2017-11-23 20:44 ` Antoine Beaupré
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=20171022153634.14802-1-dkg@fifthhorseman.net \
--to=dkg@fifthhorseman.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).