Re: privacy problem: text/html parts pull in network resources
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Thu, 29 Jan 2015 18:03:43 +0000 (13:03 +1900)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 21:47:53 +0000 (14:47 -0700)
a2/73212a77f7be2d4dbab555002f8ae1beeb9da9 [new file with mode: 0644]

diff --git a/a2/73212a77f7be2d4dbab555002f8ae1beeb9da9 b/a2/73212a77f7be2d4dbab555002f8ae1beeb9da9
new file mode 100644 (file)
index 0000000..a28bb9a
--- /dev/null
@@ -0,0 +1,74 @@
+Return-Path: <dkg@fifthhorseman.net>\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 C4E29431FC4\r
+       for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 10:03:52 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: 2.438\r
+X-Spam-Level: **\r
+X-Spam-Status: No, score=2.438 tagged_above=-999 required=5\r
+       tests=[DNS_FROM_AHBL_RHSBL=2.438] 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 otqU+He0Q409 for <notmuch@notmuchmail.org>;\r
+       Thu, 29 Jan 2015 10:03:49 -0800 (PST)\r
+Received: from che.mayfirst.org (che.mayfirst.org [209.234.253.108])\r
+       by olra.theworths.org (Postfix) with ESMTP id 95576431FBC\r
+       for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 10:03:49 -0800 (PST)\r
+Received: from fifthhorseman.net (unknown [38.109.115.130])\r
+       by che.mayfirst.org (Postfix) with ESMTPSA id 7E71AF984\r
+       for <notmuch@notmuchmail.org>; Thu, 29 Jan 2015 13:03:44 -0500 (EST)\r
+Received: by fifthhorseman.net (Postfix, from userid 1000)\r
+       id 76109201D1; Thu, 29 Jan 2015 13:03:43 -0500 (EST)\r
+From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>\r
+To: notmuch mailing list <notmuch@notmuchmail.org>\r
+Subject: Re: privacy problem: text/html parts pull in network resources\r
+In-Reply-To: <yq65386uqx0a.fsf@jinwoo-macbookair.roam.corp.google.com>\r
+References: <87ppa7q25w.fsf@alice.fifthhorseman.net>\r
+       <87fvay3g0g.fsf@maritornes.cs.unb.ca>\r
+       <871tmfin1k.fsf@alice.fifthhorseman.net>\r
+       <yq65h9vbtsyt.fsf@jinwoo-macbookair.roam.corp.google.com>\r
+       <yq65386uqx0a.fsf@jinwoo-macbookair.roam.corp.google.com>\r
+User-Agent: Notmuch/0.18.2 (http://notmuchmail.org) Emacs/24.4.1\r
+       (x86_64-pc-linux-gnu)\r
+Date: Thu, 29 Jan 2015 13:03:43 -0500\r
+Message-ID: <87wq45cvls.fsf@alice.fifthhorseman.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\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: Thu, 29 Jan 2015 18:03:52 -0000\r
+\r
+On Wed 2015-01-28 18:57:25 -0500, Jinwoo Lee wrote:\r
+> Do you mind if I add a boolean defcustom, which determines whether to\r
+> block remote images?  Its default value will be T (block), but people\r
+> who want to see remote images can customize it.\r
+\r
+I have no objection to this kind of knob in an already fiddly config\r
+space.  In the other thread, i see the discussion of whether this should\r
+expose something fancier than a boolean, but given the number of\r
+possible rendering backends, i don't know how well we can support any of\r
+these options reliably.\r
+\r
+What should notmuch do when the customization variable is set to t\r
+(block remote images) but the html rendering backend doesn't support\r
+blocking remote images?\r
+\r
+It seems dangerous/disingenuous to offer the option to the user but not\r
+be able to enforce it in this case.  Should having this set to t\r
+restrict the range of html renderers to only those that we can force to\r
+respect it?\r
+\r
+        --dkg\r