unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jeremy Nickurak <not-much@trk.nickurak.ca>
To: Jameson Graef Rollins <jrollins@finestructure.net>
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, 7 Apr 2014 14:15:38 -0600	[thread overview]
Message-ID: <CA+eQo_3hUAc3uMWw6Hb2JLBATiBDS96GozCa5jqT_1sWz1Y=hQ@mail.gmail.com> (raw)
In-Reply-To: <87ob0dnndk.fsf@servo.finestructure.net>

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

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.


On Mon, Apr 7, 2014 at 9:57 AM, Jameson Graef Rollins <
jrollins@finestructure.net> wrote:

> On Mon, Apr 07 2014, john.wyzer@gmx.de wrote:
> >> confess i haven't been following closely), it wouldn't be much extra
> >> effort for someone to implement a filter that strips encryption from the
> >> message.  (this might still have the problem mentioned above about also
> >> stripping PGP/MIME signatures, but the signatures and the decrypted
> >> message itself would remain intact so they could be shown directly by
> >> notmuch show without trouble).
> >
> > I don't understand that. :-(
> > This sounds as if the view of the message is not generated from the
> > mail storage. Isn't the purpose of the index to find the appropriate
> > message file and everything else is generated from that file?
>
> I think that's exactly what Daniel is saying: what's viewed comes from
> the message directly, and not from the db.
>
> jamie.
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
>
>

[-- Attachment #2: Type: text/html, Size: 1982 bytes --]

  reply	other threads:[~2014-04-07 20:15 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 [this message]
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='CA+eQo_3hUAc3uMWw6Hb2JLBATiBDS96GozCa5jqT_1sWz1Y=hQ@mail.gmail.com' \
    --to=not-much@trk.nickurak.ca \
    --cc=dkg@debian.org \
    --cc=dkg@fifthhorseman.net \
    --cc=jrollins@finestructure.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).