Re: a DoS vulnerability associated with conflated Message-IDs?
authorJeremy Nickurak <not-much@trk.nickurak.ca>
Thu, 8 Mar 2012 17:38:32 +0000 (10:38 +1700)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:45:19 +0000 (09:45 -0800)
87/b71206af039e4a2f4fd5eb7e4233e38d3d6a69 [new file with mode: 0644]

diff --git a/87/b71206af039e4a2f4fd5eb7e4233e38d3d6a69 b/87/b71206af039e4a2f4fd5eb7e4233e38d3d6a69
new file mode 100644 (file)
index 0000000..42da0f9
--- /dev/null
@@ -0,0 +1,74 @@
+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 CFCC3431FB6\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 09:38:33 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7]\r
+       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 dyJJWOecBCvv for <notmuch@notmuchmail.org>;\r
+       Thu,  8 Mar 2012 09:38:33 -0800 (PST)\r
+Received: from mail-pz0-f53.google.com (mail-pz0-f53.google.com\r
+       [209.85.210.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 3F02B431FAE\r
+       for <notmuch@notmuchmail.org>; Thu,  8 Mar 2012 09:38:33 -0800 (PST)\r
+Received: by dady25 with SMTP id y25so728800dad.26\r
+       for <notmuch@notmuchmail.org>; Thu, 08 Mar 2012 09:38:32 -0800 (PST)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+       d=nickurak.ca; s=google-dkim;\r
+       h=mime-version:sender:x-originating-ip:in-reply-to:references:date\r
+       :x-google-sender-auth:message-id:subject:from:to:content-type;\r
+       bh=Il3a+ueWmxLt8LGWvwNlT/SPmvfwUTNPQrKBsmujjco=;\r
+       b=O1TP+mn41RkuiG7csH40eRZh3xmE7mWza8EB5gUqJv6l3wMqLO5y8IK1IJDBwPdLjQ\r
+       b4xkoW7YQuDXyomQGNXtVtDr9bePnIs3dolCg1MIKkYzsaFJ2Mo/kd74z8kd/Vu2ZDBj\r
+       qg59QIjZgLyB0/hUQiAx0PUq7AVdepBjg7T5E=\r
+MIME-Version: 1.0\r
+Received: by 10.68.216.138 with SMTP id oq10mr10919223pbc.85.1331228312506;\r
+       Thu, 08 Mar 2012 09:38:32 -0800 (PST)\r
+Sender: jeremy@nickurak.ca\r
+Received: by 10.68.228.42 with HTTP; Thu, 8 Mar 2012 09:38:32 -0800 (PST)\r
+X-Originating-IP: [128.221.197.58]\r
+In-Reply-To: <4F58E962.1050403@fifthhorseman.net>\r
+References: <87k42vrqve.fsf@pip.fifthhorseman.net>\r
+       <87ipif2fdn.fsf@wyzanski.jamesvasile.com>\r
+       <4F58E962.1050403@fifthhorseman.net>\r
+Date: Thu, 8 Mar 2012 10:38:32 -0700\r
+X-Google-Sender-Auth: 1_sl2UIMbywzGKvatmc9BLQsNR8\r
+Message-ID:\r
+ <CA+eQo_3x+VJMoB1U1R-vvk==u4x6drKikHrr=HHZZnsZEE7PmQ@mail.gmail.com>\r
+Subject: Re: a DoS vulnerability associated with conflated Message-IDs?\r
+From: Jeremy Nickurak <not-much@trk.nickurak.ca>\r
+To: notmuch <notmuch@notmuchmail.org>\r
+Content-Type: text/plain; charset=UTF-8\r
+X-Gm-Message-State:\r
+ ALoCoQlwAw35DwXun8NdZPPp1qUUcc0H16M8Bhm5+7GysyXehkbmpiHYf1uOiBEQ4nQr8eAQ3mea\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, 08 Mar 2012 17:38:33 -0000\r
+\r
+On Thu, Mar 8, 2012 at 10:16, Daniel Kahn Gillmor <dkg@fifthhorseman.net> wrote:\r
+> Any other suggestions or ideas?\r
+\r
+What about representing the contents from both message in one apparent message?\r
+\r
+- Aggregate the headers together, perhaps?\r
+- Where headers disagree, display both\r
+- If the bodies disagree, display both.\r