Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs: switching mode= to invalid value...
authorDavid Edmondson <dme@dme.org>
Mon, 8 Feb 2016 17:52:01 +0000 (17:52 +0000)
committerW. Trevor King <wking@tremily.us>
Sat, 20 Aug 2016 23:21:02 +0000 (16:21 -0700)
fe/095b3aa8175d594ac89f70e1bbf1f7cf25acd9 [new file with mode: 0644]

diff --git a/fe/095b3aa8175d594ac89f70e1bbf1f7cf25acd9 b/fe/095b3aa8175d594ac89f70e1bbf1f7cf25acd9
new file mode 100644 (file)
index 0000000..d102b4a
--- /dev/null
@@ -0,0 +1,120 @@
+Return-Path: <dme@dme.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id 5B3BB6DE0AC2\r
+ for <notmuch@notmuchmail.org>; Mon,  8 Feb 2016 09:52:08 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.019\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[AWL=0.048,\r
+  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7,\r
+ RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.652,\r
+ UNPARSEABLE_RELAY=0.001] autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id OcSriH9B2FFC for <notmuch@notmuchmail.org>;\r
+ Mon,  8 Feb 2016 09:52:06 -0800 (PST)\r
+Received: from mail-wm0-f44.google.com (mail-wm0-f44.google.com\r
+ [74.125.82.44]) by arlo.cworth.org (Postfix) with ESMTPS id B039E6DE02CE for\r
+ <notmuch@notmuchmail.org>; Mon,  8 Feb 2016 09:52:05 -0800 (PST)\r
+Received: by mail-wm0-f44.google.com with SMTP id p63so126659237wmp.1\r
+ for <notmuch@notmuchmail.org>; Mon, 08 Feb 2016 09:52:05 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=dme-org.20150623.gappssmtp.com; s=20150623;\r
+ h=to:subject:in-reply-to:references:from:date:message-id:mime-version\r
+ :content-type; bh=TuVZef+PxHVtmwQncrQ0raVTVn2gbGkg7CWR23N52b4=;\r
+ b=pHceJ9zhD5dGpZ3ti6GJ7EWQcLV1fiOVAPIpWJnJiWPhRHZI52dQ7sbbXsqsgkVzMI\r
+ +dyIMeWxgiEmYh84hLbjxVt0TWYXRBv+Ky82yEV6EbdwzEkhr7MXLG3cGkXGPp8FIY9Y\r
+ sgGC6IibCG1sZUkGelnIiUZkuZd9yTkhPWHViAD/mWaG4kvYMls/yq31iBk9phuv198D\r
+ CMFrVwyiECTPfbNji8F7zQDwgGkHT0wmvMQGT/f8JprmcdLcpUisKhlsNW4XATzHyG48\r
+ kfhtGDHOAE8HjjtmF7Yx5wPH1cP4Uz/Bs0SjzHLA8TFS7jbyn6pX2eWrS8e5N0w704HN\r
+ voig==\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:to:subject:in-reply-to:references:from:date\r
+ :message-id:mime-version:content-type;\r
+ bh=TuVZef+PxHVtmwQncrQ0raVTVn2gbGkg7CWR23N52b4=;\r
+ b=bABuPQSfC/wdshK46SQvTuotckMAUV2iWkDHpHVurPtmC1AzRYDf3QNoBuj8plqc2F\r
+ 3z41jSj8C6MLejz0p3Mks4oEnXoK5n4Q8CrSzKuaNPOEDWVBXZ1074ARkRPLHab+sTjY\r
+ yoaZcZRnkqpG/NqD7c+ITmHZ7Tcp+4LBemT4z7wIB/izuwcVQZhutXvrOkpWaczhGaoU\r
+ btRm8Prd4LgRMhCWRe+ELLOl/mOfNa0SwVTpbrCZ4tqS5VmbPxzs+C0EmSsTQGIPOPkM\r
+ NHgPHuwvpeJNY0N/GfE0myG8k+MGPCpiURJV0a54oL7pKvbP7eDjEg/turvWqz8GyozU\r
+ t/Pw==\r
+X-Gm-Message-State:\r
+ AG10YOS67+bp9YsE+aLkk+iSxiBJHCK2MVDgW+0WwATz2KjwAaG7QSV2XZpt6wcxsjQqwg==\r
+X-Received: by 10.28.72.197 with SMTP id v188mr122763wma.34.1454953924344;\r
+ Mon, 08 Feb 2016 09:52:04 -0800 (PST)\r
+Received: from disaster-area.hh.sledj.net\r
+ ([2a01:348:1a2:1:ea39:35ff:fe2c:a227])\r
+ by smtp.gmail.com with ESMTPSA id c185sm13708381wma.5.2016.02.08.09.52.02\r
+ (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);\r
+ Mon, 08 Feb 2016 09:52:02 -0800 (PST)\r
+Received: from localhost (disaster-area.hh.sledj.net [local])\r
+ by disaster-area.hh.sledj.net (OpenSMTPD) with ESMTPA id 8a9c7d20;\r
+ Mon, 8 Feb 2016 17:52:01 +0000 (UTC)\r
+To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org,\r
+ 759646@bugs.debian.org\r
+Subject: Re: [Vagrant Cascadian] Bug#759646: notmuch-emacs:\r
+ switching     mode=   to      invalid value sends unencrypted mail\r
+In-Reply-To: <87egsldds6.fsf@maritornes.cs.unb.ca>\r
+References: <87lhq7npcw.fsf@maritornes.cs.unb.ca> <87k35q2zso.fsf@nikula.org>\r
+ <54055C53.40604@fifthhorseman.net> <m238caa1rk.fsf@guru.guru-group.fi>\r
+ <cunzjbwi36y.fsf@gargravarr.hh.sledj.net>\r
+ <87egsldds6.fsf@maritornes.cs.unb.ca>\r
+From: David Edmondson <dme@dme.org>\r
+Date: Mon, 08 Feb 2016 17:52:01 +0000\r
+Message-ID: <m2lh6v3xa6.fsf@heart-of-gold.hh.sledj.net>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 08 Feb 2016 17:52:08 -0000\r
+\r
+[Raking over history...]\r
+\r
+On Sat, Nov 29 2014, David Bremner wrote:\r
+> David Edmondson <dme@dme.org> writes:\r
+>\r
+>> On Tue, Sep 02 2014, Tomi Ollila wrote:\r
+>>> On Tue, Sep 02 2014, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+>>>\r
+>>>> On 08/30/2014 03:37 AM, Jani Nikula wrote:\r
+>>>>> I'm inclined to think this is a bug in message-mode. \r
+>>>>\r
+>>>> I agree it's a bug in message-mode, not in notmuch itself.\r
+>>>\r
+>>> I think it might be here:\r
+>>>\r
+>>> http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/head:/lisp/gnus/mml.el#L258\r
+>>>\r
+>>> (it takes time to load, please wait...)\r
+>>>\r
+>>> If cond does not match, then don't fail...\r
+>>\r
+>> This looks to have been fixed in emacs at the end of September 2014.\r
+>\r
+> Right, this fix was released in emacs 24.4\r
+>\r
+> I'm a little torn what to do here. On the one hand the upstream change\r
+> fixes the bug as reported. On the other hand, if something corrupts the\r
+> #secure tag (e.g., by deleting a letter), then the message is still sent\r
+> un-uncrypted.\r
+\r
+That's true, but it's undoubtedly an upstream bug rather than a\r
+notmuch-emacs bug.\r
+\r
+If we apply some heuristic workaround in notmuch, users of gnus (and\r
+mu4e?) will still be vulnerable to the same problem. The right thing to\r
+do is report (and fix) the bug upstream.\r