unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: john.wyzer@gmx.de
To: Jeremy Nickurak <not-much@trk.nickurak.ca>,
	David Bremner <david@tethera.net>
Cc: Notmuch Mailing List <notmuch@notmuchmail.org>,
	Daniel Kahn Gillmor <dkg@debian.org>
Subject: Re: Feature suggestion. Indexing encrypted mail?
Date: Sat, 05 Apr 2014 21:03:04 +0200	[thread overview]
Message-ID: <86ha67y4yf.fsf@someserver.somewhere> (raw)
In-Reply-To: <CA+eQo_3AFofQ3gSxvce2e_d5bbaT_e00zA30xeyOxbYCpQhsNA@mail.gmail.com>

Jeremy Nickurak <not-much@trk.nickurak.ca> writes:

> Off the top of my head, you could have an encrypted index too, which you
> can only search while able to decrypt. Certainly another level of
> complexity.
>

But why add so much complexity? 

If a user decides that either transport security is enough or
additionally the hard disk is encrypted (why store an encrypted index on
an encrypted hard disk?), said user could just switch on an option in
the notmuch configuration that causes notmuch to ask for the password
before or while indexing new messages and to add decrypted messages to the
normal index as well.


The level of security would be up to the user by means of said
configuration option and those that want the convenience of searching
encrypted messages could have it.

Personally I would argue that if an attacker has the means to access the
content of my hard disk either via the network or physically, there is
no difference between having whole disk encryption and storing an
encrypted index...

  reply	other threads:[~2014-04-05 19:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 16:38 Feature suggestion. Indexing encrypted mail? john.wyzer
2014-04-05 17:10 ` David Bremner
2014-04-05 18:35   ` Jeremy Nickurak
2014-04-05 19:03     ` john.wyzer [this message]
2014-04-05 19:09   ` Jameson Graef Rollins
2014-04-06  9:15     ` Guyzmo
2014-04-06 22:16       ` Daniel Kahn Gillmor
2014-04-07  8:08         ` john.wyzer
2014-04-07 15:57           ` Jameson Graef Rollins
2014-04-07 20:15             ` Jeremy Nickurak
2014-04-07 20:31               ` Jameson Graef Rollins
2014-04-07 21:06               ` Mark Walters
2014-04-08  5:25                 ` 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=86ha67y4yf.fsf@someserver.somewhere \
    --to=john.wyzer@gmx.de \
    --cc=david@tethera.net \
    --cc=dkg@debian.org \
    --cc=not-much@trk.nickurak.ca \
    --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).