Re: Feature suggestion. Indexing encrypted mail?

diff --git a/de/6a100f815535790f472b08425388518076b5bc b/de/6a100f815535790f472b08425388518076b5bc
new file mode 100644 (file)
index 0000000..c456cfc
--- /dev/null
+++ b/de/6a100f815535790f472b08425388518076b5bc
@@ -0,0 +1,159 @@
+Return-Path: <jeremy@nickurak.ca>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 19CCF431FAF\r
+       for <notmuch@notmuchmail.org>; Sat,  5 Apr 2014 11:35:30 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.699\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001,\r
+       RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id woIo+HywijDA for <notmuch@notmuchmail.org>;\r
+       Sat,  5 Apr 2014 11:35:18 -0700 (PDT)\r
+Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com\r
+       [209.85.212.177]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 71466431FAE\r
+       for <notmuch@notmuchmail.org>; Sat,  5 Apr 2014 11:35:18 -0700 (PDT)\r
+Received: by mail-wi0-f177.google.com with SMTP id cc10so2948724wib.4\r
+       for <notmuch@notmuchmail.org>; Sat, 05 Apr 2014 11:35:14 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=nickurak.ca; s=google-dkim;\r
+       h=mime-version:sender:in-reply-to:references:date:message-id:subject\r
+       :from:to:cc:content-type;\r
+       bh=iDej/pzKq255tYVP+E+OLnrgcHpp8KyicjMG8weudZs=;\r
+       b=YLmi1ICVtqNWEBFKmpoIZ5DK2BpJkwounRG4nKrSrk42kuf4lQ2fgEPDCP8qe3ePWP\r
+       8YqHZ02KmW5kyyuc8wL8lY7niCdzm9ButmzNCqvIg4IHDZ2q04z2eu0bJygANgAHmvzJ\r
+       ITv3PdyPGPJEfS+OQnuXsEDehGJbn53FKVxbY=\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=1e100.net; s=20130820;\r
+       h=x-gm-message-state:mime-version:sender:in-reply-to:references:date\r
+       :message-id:subject:from:to:cc:content-type;\r
+       bh=iDej/pzKq255tYVP+E+OLnrgcHpp8KyicjMG8weudZs=;\r
+       b=hq07RD7F6/pYWU4k9PTk/Euzwbubf0Vg/k012cVDggsj7qhfYJEYzjmZ6mWjIk0edx\r
+       /J/xxmg2JeFpiHV/sI24RWbvLIZ+/wMgXwX00CJGEX7B4aQARLqFZrLGGsxDlzN+IJNN\r
+       iWoyporPi3xdHBSZ1vENZeOS15TfYxtMV/qfHUmBjz7b5QWthDH3v/BaNMUddtVP9xpD\r
+       6SUufXstFcGPE7TStyoU9M9H6nZ+Neb2qb5f9tqHkOhRy24tCAFhL50Fg+iqqOysFGBo\r
+       xtfB4KgQfP2tqNw6cUiyneXbWVWJH4wAAak6zExNm1L1HXClKhU/Am8jZJcJ49wRUq84\r
+       qm7g==\r
+X-Gm-Message-State:\r
+ ALoCoQnmdgUYurTo0KYZCp/6+0E3mgwTcG7HF6UZcV3HBuja6x3XeRl4fDuHQiRw8XZrD3KCyMGW\r
+MIME-Version: 1.0\r
+X-Received: by 10.194.203.2 with SMTP id km2mr29701491wjc.72.1396722914574;\r
+       Sat, 05 Apr 2014 11:35:14 -0700 (PDT)\r
+Sender: jeremy@nickurak.ca\r
+Received: by 10.216.122.200 with HTTP; Sat, 5 Apr 2014 11:35:14 -0700 (PDT)\r
+X-Originating-IP: [96.52.225.98]\r
+In-Reply-To: <878urj1z3j.fsf@maritornes.cs.unb.ca>\r
+References: <86k3b3ybo6.fsf@someserver.somewhere>\r
+       <878urj1z3j.fsf@maritornes.cs.unb.ca>\r
+Date: Sat, 5 Apr 2014 12:35:14 -0600\r
+X-Google-Sender-Auth: TXJOBCrA3fKEWvkN2XthR_b8eAc\r
+Message-ID:\r
+ <CA+eQo_3AFofQ3gSxvce2e_d5bbaT_e00zA30xeyOxbYCpQhsNA@mail.gmail.com>\r
+Subject: Re: Feature suggestion. Indexing encrypted mail?\r
+From: Jeremy Nickurak <not-much@trk.nickurak.ca>\r
+To: David Bremner <david@tethera.net>\r
+Content-Type: multipart/alternative; boundary=047d7b8736ec2c5e5004f64fe506\r
+Cc: Notmuch Mailing List <notmuch@notmuchmail.org>,\r
+       Daniel Kahn Gillmor <dkg@debian.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Sat, 05 Apr 2014 18:35:30 -0000\r
+\r
+--047d7b8736ec2c5e5004f64fe506\r
+Content-Type: text/plain; charset=UTF-8\r
+\r
+Off the top of my head, you could have an encrypted index too, which you\r
+can only search while able to decrypt. Certainly another level of\r
+complexity.\r
+\r
+\r
+On Sat, Apr 5, 2014 at 11:10 AM, David Bremner <david@tethera.net> wrote:\r
+\r
+> john.wyzer@gmx.de writes:\r
+>\r
+> > Would it be possible to add the configurable option to also decrypt\r
+> > encrypted messages on the fly while indexing to make them searchable,\r
+> > too?\r
+> >\r
+> > That would be really great for people that consider gnupg  mainly an\r
+> > encryption for transport or have their complete hard drive encrypted...\r
+>\r
+> As far I understand an attacker could reconstruct the message from the\r
+> index, so one question is whether the extra complexity in notmuch is\r
+> worth the minimal extra security over decrypting on delivery and storing\r
+> plaintext on the (presumably encrypted) disk. Of course decrypting on\r
+> delivery may be inconvenient (or impossible). I have CCed the two people\r
+> who have implemented most of the crypto related stuff in notmuch so they\r
+> can comment.\r
+>\r
+> d\r
+> _______________________________________________\r
+> notmuch mailing list\r
+> notmuch@notmuchmail.org\r
+> http://notmuchmail.org/mailman/listinfo/notmuch\r
+>\r
+\r
+--047d7b8736ec2c5e5004f64fe506\r
+Content-Type: text/html; charset=UTF-8\r
+Content-Transfer-Encoding: quoted-printable\r
+\r
+<div dir=3D"ltr">Off the top of my head, you could have an encrypted index =\r
+too, which you can only search while able to decrypt. Certainly another lev=\r
+el of complexity.</div><div class=3D"gmail_extra"><br><br><div class=3D"gma=\r
+il_quote">\r
+On Sat, Apr 5, 2014 at 11:10 AM, David Bremner <span dir=3D"ltr">&lt;<a hre=\r
+f=3D"mailto:david@tethera.net" target=3D"_blank">david@tethera.net</a>&gt;<=\r
+/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=\r
+ex;border-left:1px #ccc solid;padding-left:1ex">\r
+<div class=3D""><a href=3D"mailto:john.wyzer@gmx.de">john.wyzer@gmx.de</a> =\r
+writes:<br>\r
+<br>\r
+&gt; Would it be possible to add the configurable option to also decrypt<br=\r
+>\r
+&gt; encrypted messages on the fly while indexing to make them searchable,<=\r
+br>\r
+&gt; too?<br>\r
+&gt;<br>\r
+&gt; That would be really great for people that consider gnupg =C2=A0mainly=\r
+ an<br>\r
+&gt; encryption for transport or have their complete hard drive encrypted..=\r
+.<br>\r
+<br>\r
+</div>As far I understand an attacker could reconstruct the message from th=\r
+e<br>\r
+index, so one question is whether the extra complexity in notmuch is<br>\r
+worth the minimal extra security over decrypting on delivery and storing<br=\r
+>\r
+plaintext on the (presumably encrypted) disk. Of course decrypting on<br>\r
+delivery may be inconvenient (or impossible). I have CCed the two people<br=\r
+>\r
+who have implemented most of the crypto related stuff in notmuch so they<br=\r
+>\r
+can comment.<br>\r
+<div class=3D"HOEnZb"><div class=3D"h5"><br>\r
+d<br>\r
+_______________________________________________<br>\r
+notmuch mailing list<br>\r
+<a href=3D"mailto:notmuch@notmuchmail.org">notmuch@notmuchmail.org</a><br>\r
+<a href=3D"http://notmuchmail.org/mailman/listinfo/notmuch" target=3D"_blan=\r
+k">http://notmuchmail.org/mailman/listinfo/notmuch</a><br>\r
+</div></div></blockquote></div><br></div>\r
+\r
+--047d7b8736ec2c5e5004f64fe506--\r