From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 3DD7C431FBC for ; Mon, 7 Apr 2014 13:15:47 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.699 X-Spam-Level: X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f-zNb80xr+hA for ; Mon, 7 Apr 2014 13:15:43 -0700 (PDT) Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com [74.125.82.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id CE78B431FB6 for ; Mon, 7 Apr 2014 13:15:42 -0700 (PDT) Received: by mail-wg0-f52.google.com with SMTP id k14so7284461wgh.11 for ; Mon, 07 Apr 2014 13:15:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nickurak.ca; s=google-dkim; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=LKxfFXILWwQZzNgaC9b4Rgy6I6SfN53YYA6O8poG1vg=; b=iD9LlLvvAGo+n5PkfdFD9FHw1eFrkhACC8hJxU7IKvxH0ffkjsUJS2s8/7O/x08BhN TSpndMgCJwqqLqTokMhoeGkpWB5mmHoy825ZJtUMdODKDIS3bX1jafhQ2NicPuqIuqTR aTgfxjgE7O+211VrzZ/ELy2mnQ4qkLejkIxr8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=LKxfFXILWwQZzNgaC9b4Rgy6I6SfN53YYA6O8poG1vg=; b=OhDCG+avvyech26PBBFAMti3D76iWfyf7tdW1dOv8PzJZsvlK32vrRYe8rsJClCo2T HTbUblev52E28/8RwkeSb8XucMg8vhELxb/Kx9D/mP/fz4jVnZ1eEJ0VVV+J3riQoVif hOdsQcnbIWDoWeEAIidSkksnOdC8Fng25SGYtYCrUun6J5bW76FvI4ZjpGswVnGDg2AL Gq7L0PK6iJ5IK/W1mM61nbxkmhEuKdLrdmt2SEX1yruJ7xuUzz5tAKI3aUU1NDN3HnXc nxZ2tqfxMJ6+E7V+DPTMq0Tl1nqXfutL906CLRbxPFfFstoGOIdIwso1rpdQMTYJ/2GR g4QQ== X-Gm-Message-State: ALoCoQn/ApUEs9h2ZoPmWspDAMrXjSaEzX/MFm7ZudpbGh1HDTciXN+HxQp3Ry/+c1n+S4iEOhJf MIME-Version: 1.0 X-Received: by 10.180.187.16 with SMTP id fo16mr27651365wic.26.1396901738620; Mon, 07 Apr 2014 13:15:38 -0700 (PDT) Sender: jeremy@nickurak.ca Received: by 10.216.122.200 with HTTP; Mon, 7 Apr 2014 13:15:38 -0700 (PDT) X-Originating-IP: [96.52.225.98] In-Reply-To: <87ob0dnndk.fsf@servo.finestructure.net> References: <86k3b3ybo6.fsf@someserver.somewhere> <878urj1z3j.fsf@maritornes.cs.unb.ca> <87txa7pp8z.fsf@servo.finestructure.net> <20140406091516.GG26903@vilya.m0g.net> <5341D252.90405@fifthhorseman.net> <867g71y327.fsf@someserver.somewhere> <87ob0dnndk.fsf@servo.finestructure.net> Date: Mon, 7 Apr 2014 14:15:38 -0600 X-Google-Sender-Auth: 4SGmkatDRk1EbIPV5yGoeeOkIm0 Message-ID: Subject: Re: Feature suggestion. Indexing encrypted mail? From: Jeremy Nickurak To: Jameson Graef Rollins Content-Type: multipart/alternative; boundary=001a11c266c4eac32c04f6798718 Cc: Notmuch Mailing List , Daniel Kahn Gillmor , Daniel Kahn Gillmor X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 20:15:47 -0000 --001a11c266c4eac32c04f6798718 Content-Type: text/plain; charset=UTF-8 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 > > --001a11c266c4eac32c04f6798718 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Nonetheess, if you can tell from the index that a given me= ssage contains the words "hotel" "wine" "wife"= ; "secret" and "rendezvous", you can infer a *lot* abou= t 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 fr= om the
>> message. =C2=A0(this might still have the problem mentioned above = about also
>> stripping PGP/MIME signatures, but the signatures and the decrypte= d
>> 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 appropria= te
> message file and everything else is generated from that file?

I think that's exactly what Daniel is saying: what's viewed c= omes from
the message directly, and not from the db.

jamie.

_______________________________________________
notmuch mailing list
notmuch@notmuchmail.org
http://notmuchmail.org/mailman/listinfo/notmuch


--001a11c266c4eac32c04f6798718--