From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Jeremy Nickurak <not-much@trk.nickurak.ca>
Cc: Notmuch Mailing List <notmuch@notmuchmail.org>,
Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Daniel Kahn Gillmor <dkg@debian.org>
Subject: Re: Feature suggestion. Indexing encrypted mail?
Date: Mon, 07 Apr 2014 13:31:45 -0700 [thread overview]
Message-ID: <87d2gsop8u.fsf@servo.finestructure.net> (raw)
In-Reply-To: <CA+eQo_3hUAc3uMWw6Hb2JLBATiBDS96GozCa5jqT_1sWz1Y=hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On Mon, Apr 07 2014, Jeremy Nickurak <not-much@trk.nickurak.ca> wrote:
> Nonetheess, if you can tell from the index that a given message contains
> the words "hotel" "wine" "wife" "secret" and "rendezvous", you can infer a
> *lot* about the contents of encrypted contents of the message.
Of course. Given that the content of the message will be stored
unencrypted in the db, indexing encrypted messages is potentially a foot
gun. If we were to enable a feature like this, it would definitely be a
user-beware situation. I don't see any way around that.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-04-07 20:31 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
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 [this message]
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=87d2gsop8u.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=dkg@debian.org \
--cc=dkg@fifthhorseman.net \
--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).