1 Return-Path: <jeremy@nickurak.ca>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 3DD7C431FBC
\r
6 for <notmuch@notmuchmail.org>; Mon, 7 Apr 2014 13:15:47 -0700 (PDT)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001,
\r
13 RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id f-zNb80xr+hA for <notmuch@notmuchmail.org>;
\r
17 Mon, 7 Apr 2014 13:15:43 -0700 (PDT)
\r
18 Received: from mail-wg0-f52.google.com (mail-wg0-f52.google.com
\r
19 [74.125.82.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client
\r
20 certificate requested) by olra.theworths.org (Postfix) with ESMTPS id
\r
21 CE78B431FB6 for <notmuch@notmuchmail.org>; Mon, 7 Apr 2014 13:15:42 -0700
\r
23 Received: by mail-wg0-f52.google.com with SMTP id k14so7284461wgh.11
\r
24 for <notmuch@notmuchmail.org>; Mon, 07 Apr 2014 13:15:39 -0700 (PDT)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
26 d=nickurak.ca; s=google-dkim;
\r
27 h=mime-version:sender:in-reply-to:references:date:message-id:subject
\r
28 :from:to:cc:content-type;
\r
29 bh=LKxfFXILWwQZzNgaC9b4Rgy6I6SfN53YYA6O8poG1vg=;
\r
30 b=iD9LlLvvAGo+n5PkfdFD9FHw1eFrkhACC8hJxU7IKvxH0ffkjsUJS2s8/7O/x08BhN
\r
31 TSpndMgCJwqqLqTokMhoeGkpWB5mmHoy825ZJtUMdODKDIS3bX1jafhQ2NicPuqIuqTR
\r
32 aTgfxjgE7O+211VrzZ/ELy2mnQ4qkLejkIxr8=
\r
33 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
34 d=1e100.net; s=20130820;
\r
35 h=x-gm-message-state:mime-version:sender:in-reply-to:references:date
\r
36 :message-id:subject:from:to:cc:content-type;
\r
37 bh=LKxfFXILWwQZzNgaC9b4Rgy6I6SfN53YYA6O8poG1vg=;
\r
38 b=OhDCG+avvyech26PBBFAMti3D76iWfyf7tdW1dOv8PzJZsvlK32vrRYe8rsJClCo2T
\r
39 HTbUblev52E28/8RwkeSb8XucMg8vhELxb/Kx9D/mP/fz4jVnZ1eEJ0VVV+J3riQoVif
\r
40 hOdsQcnbIWDoWeEAIidSkksnOdC8Fng25SGYtYCrUun6J5bW76FvI4ZjpGswVnGDg2AL
\r
41 Gq7L0PK6iJ5IK/W1mM61nbxkmhEuKdLrdmt2SEX1yruJ7xuUzz5tAKI3aUU1NDN3HnXc
\r
42 nxZ2tqfxMJ6+E7V+DPTMq0Tl1nqXfutL906CLRbxPFfFstoGOIdIwso1rpdQMTYJ/2GR
\r
45 ALoCoQn/ApUEs9h2ZoPmWspDAMrXjSaEzX/MFm7ZudpbGh1HDTciXN+HxQp3Ry/+c1n+S4iEOhJf
\r
47 X-Received: by 10.180.187.16 with SMTP id fo16mr27651365wic.26.1396901738620;
\r
48 Mon, 07 Apr 2014 13:15:38 -0700 (PDT)
\r
49 Sender: jeremy@nickurak.ca
\r
50 Received: by 10.216.122.200 with HTTP; Mon, 7 Apr 2014 13:15:38 -0700 (PDT)
\r
51 X-Originating-IP: [96.52.225.98]
\r
52 In-Reply-To: <87ob0dnndk.fsf@servo.finestructure.net>
\r
53 References: <86k3b3ybo6.fsf@someserver.somewhere>
\r
54 <878urj1z3j.fsf@maritornes.cs.unb.ca>
\r
55 <87txa7pp8z.fsf@servo.finestructure.net>
\r
56 <20140406091516.GG26903@vilya.m0g.net>
\r
57 <5341D252.90405@fifthhorseman.net>
\r
58 <867g71y327.fsf@someserver.somewhere>
\r
59 <87ob0dnndk.fsf@servo.finestructure.net>
\r
60 Date: Mon, 7 Apr 2014 14:15:38 -0600
\r
61 X-Google-Sender-Auth: 4SGmkatDRk1EbIPV5yGoeeOkIm0
\r
63 <CA+eQo_3hUAc3uMWw6Hb2JLBATiBDS96GozCa5jqT_1sWz1Y=hQ@mail.gmail.com>
\r
64 Subject: Re: Feature suggestion. Indexing encrypted mail?
\r
65 From: Jeremy Nickurak <not-much@trk.nickurak.ca>
\r
66 To: Jameson Graef Rollins <jrollins@finestructure.net>
\r
67 Content-Type: multipart/alternative; boundary=001a11c266c4eac32c04f6798718
\r
68 Cc: Notmuch Mailing List <notmuch@notmuchmail.org>,
\r
69 Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
\r
70 Daniel Kahn Gillmor <dkg@debian.org>
\r
71 X-BeenThere: notmuch@notmuchmail.org
\r
72 X-Mailman-Version: 2.1.13
\r
74 List-Id: "Use and development of the notmuch mail system."
\r
75 <notmuch.notmuchmail.org>
\r
76 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
77 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
78 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
79 List-Post: <mailto:notmuch@notmuchmail.org>
\r
80 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
81 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
82 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
83 X-List-Received-Date: Mon, 07 Apr 2014 20:15:47 -0000
\r
85 --001a11c266c4eac32c04f6798718
\r
86 Content-Type: text/plain; charset=UTF-8
\r
88 Nonetheess, if you can tell from the index that a given message contains
\r
89 the words "hotel" "wine" "wife" "secret" and "rendezvous", you can infer a
\r
90 *lot* about the contents of encrypted contents of the message.
\r
93 On Mon, Apr 7, 2014 at 9:57 AM, Jameson Graef Rollins <
\r
94 jrollins@finestructure.net> wrote:
\r
96 > On Mon, Apr 07 2014, john.wyzer@gmx.de wrote:
\r
97 > >> confess i haven't been following closely), it wouldn't be much extra
\r
98 > >> effort for someone to implement a filter that strips encryption from the
\r
99 > >> message. (this might still have the problem mentioned above about also
\r
100 > >> stripping PGP/MIME signatures, but the signatures and the decrypted
\r
101 > >> message itself would remain intact so they could be shown directly by
\r
102 > >> notmuch show without trouble).
\r
104 > > I don't understand that. :-(
\r
105 > > This sounds as if the view of the message is not generated from the
\r
106 > > mail storage. Isn't the purpose of the index to find the appropriate
\r
107 > > message file and everything else is generated from that file?
\r
109 > I think that's exactly what Daniel is saying: what's viewed comes from
\r
110 > the message directly, and not from the db.
\r
114 > _______________________________________________
\r
115 > notmuch mailing list
\r
116 > notmuch@notmuchmail.org
\r
117 > http://notmuchmail.org/mailman/listinfo/notmuch
\r
121 --001a11c266c4eac32c04f6798718
\r
122 Content-Type: text/html; charset=UTF-8
\r
123 Content-Transfer-Encoding: quoted-printable
\r
125 <div dir=3D"ltr">Nonetheess, if you can tell from the index that a given me=
\r
126 ssage contains the words "hotel" "wine" "wife"=
\r
127 ; "secret" and "rendezvous", you can infer a *lot* abou=
\r
128 t the contents of encrypted contents of the message.</div>
\r
129 <div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon, Apr 7=
\r
130 , 2014 at 9:57 AM, Jameson Graef Rollins <span dir=3D"ltr"><<a href=3D"m=
\r
131 ailto:jrollins@finestructure.net" target=3D"_blank">jrollins@finestructure.=
\r
132 net</a>></span> wrote:<br>
\r
133 <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
\r
134 x #ccc solid;padding-left:1ex"><div class=3D"">On Mon, Apr 07 2014, <a href=
\r
135 =3D"mailto:john.wyzer@gmx.de">john.wyzer@gmx.de</a> wrote:<br>
\r
136 >> confess i haven't been following closely), it wouldn't be =
\r
138 >> effort for someone to implement a filter that strips encryption fr=
\r
140 >> message. =C2=A0(this might still have the problem mentioned above =
\r
142 >> stripping PGP/MIME signatures, but the signatures and the decrypte=
\r
144 >> message itself would remain intact so they could be shown directly=
\r
146 >> notmuch show without trouble).<br>
\r
148 > I don't understand that. :-(<br>
\r
149 > This sounds as if the view of the message is not generated from the<br=
\r
151 > mail storage. Isn't the purpose of the index to find the appropria=
\r
153 > message file and everything else is generated from that file?<br>
\r
155 </div>I think that's exactly what Daniel is saying: what's viewed c=
\r
157 the message directly, and not from the db.<br>
\r
160 <br>_______________________________________________<br>
\r
161 notmuch mailing list<br>
\r
162 <a href=3D"mailto:notmuch@notmuchmail.org">notmuch@notmuchmail.org</a><br>
\r
163 <a href=3D"http://notmuchmail.org/mailman/listinfo/notmuch" target=3D"_blan=
\r
164 k">http://notmuchmail.org/mailman/listinfo/notmuch</a><br>
\r
165 <br></blockquote></div><br></div>
\r
167 --001a11c266c4eac32c04f6798718--
\r