Re: [dmarc-ietf] ARC-Seal is meaningless security theatre

"Murray S. Kucherawy" <superuser@gmail.com> Sat, 19 August 2017 01:43 UTC

Return-Path: <superuser@gmail.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C2A71252BA for <dmarc@ietfa.amsl.com>; Fri, 18 Aug 2017 18:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3f--C-QurrrZ for <dmarc@ietfa.amsl.com>; Fri, 18 Aug 2017 18:43:57 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88384132436 for <dmarc@ietf.org>; Fri, 18 Aug 2017 18:43:57 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id x77so17540243qka.5 for <dmarc@ietf.org>; Fri, 18 Aug 2017 18:43:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yxDYED/lG+rPZFejsWXKziMBSjGKdom5HweOfnS9gog=; b=DgLt5aALpaTn9WmW/m4J2Rrt3OWnESktlewvXF+M0NhfVXvAWaxEdY4lOsWpPynhd2 i3IBwfuKv5rNShCkL8h3tMnIg2A8D1iwF7jMLKPsYqB+EiqK9PPi2mcx2yG4W9TcV7Qf SzIvAliViqnCWreIlkPxAQdFXVH5i17QK+xRqVI7uog/dlB3e3ib1unWfHhDMZgaSZ0+ 7Hx7JZswo/JwONj/+8+CBDfjzcpmsS0ZexVyoU32sXvBfVnnVlyDW3u9QrI6N2hyfXO4 y2x7wNObPmB0s8etTpE0xPJ9OA8D0MZiSwgKEOj8dNkx6aKA02t4Ifj/TA+XtaTVN/nI Z0nQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yxDYED/lG+rPZFejsWXKziMBSjGKdom5HweOfnS9gog=; b=lx9i30uZqCqNZhb8b2savjv/xu4JyN67QtSmUOE6QHVdFkoCY9Zs5oV7gEf9f4HXYG 2vgXHW+u/glYuAbnDt4v640AAvkJ1oBKaVXxWwcS51iQT9hYcG/O6/19OnpVHTuRLCTh 1E5sVzEhP8SwbPTXliQXkdYL+8BFUQ6OHJ/S9p3Ch+HIepV8/8LRdRuMTYwLMw3UTOG6 msT5fR0tvHivnIAuuOIWf9SBeroFDkCvsJF0gUVhEEus97L7JRy2OPkvEn5TH9dOtDql DeImYkCpfz3l0hw9y0x+MU1nrcqZykzidnHcMqgiabvxEOvKpY9W4k3ssD3yvZGdr9zQ LrJA==
X-Gm-Message-State: AHYfb5gULNbukJp14wg0NKfM/HENfFswJqNVYQYxKLy94LXPfFXrBAvF JQmlGc8dHgzKk+wKTDtCamZoMU6Zug==
X-Received: by 10.55.47.135 with SMTP id v129mr14964630qkh.13.1503107036670; Fri, 18 Aug 2017 18:43:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.237.57.34 with HTTP; Fri, 18 Aug 2017 18:43:55 -0700 (PDT)
In-Reply-To: <CABa8R6tE7E=eEnyzfhw-veD__O4FG1s8Xf7aokjfwTFmSEzTaQ@mail.gmail.com>
References: <1502083287.2191248.1065195288.7CDC7FF3@webmail.messagingengine.com> <CABuGu1oTMbuLd4yTwecu5sKFnsmH+HiwT1FG=JpySYHzpMTx_w@mail.gmail.com> <1502200759.3946686.1066841264.607B4D0B@webmail.messagingengine.com> <2720431.u3G7bbkkxK@kitterma-e6430> <1502317564.1935379.1068588344.040173AF@webmail.messagingengine.com> <a08c7590-ded3-1642-4ffc-07848b3c6cd2@gmail.com> <e14f2130-6f00-4ef1-485b-850a4cc1c48c@gmail.com> <1502495646.4099176.1070896040.2B09B1F8@webmail.messagingengine.com> <166070f0-4ba1-70da-1f73-885b4a7f7640@gmail.com> <1502497178.4103451.1070917304.23DD466D@webmail.messagingengine.com> <598F9484.7020700@isdg.net> <CABuGu1p=oLfLRkuoaDHoz3Cv3_FrURdsFPzkac7jNzBpqBmiSg@mail.gmail.com> <599484FB.9050908@isdg.net> <1502929303.4038704.1075868960.5D80A788@webmail.messagingengine.com> <CAD2i3WN_bmDgmQBw3pnyu7vWJJM2Kzwgru87VhK=NA_H91B+og@mail.gmail.com> <1502930858.4042926.1075890568.5069945B@webmail.messagingengine.com> <CABa8R6uhV9Bs42rgUGTSetBDDFmFPOhiYa6Yuqny0gv6dT3-Kg@mail.gmail.com> <1503006397.1306110.1076933224.154E25D6@webmail.messagingengine.com> <CABa8R6tE7E=eEnyzfhw-veD__O4FG1s8Xf7aokjfwTFmSEzTaQ@mail.gmail.com>
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 18 Aug 2017 18:43:55 -0700
Message-ID: <CAL0qLwbOZ2VPYG=MLhSnHWZmbhZSuN0gU2E4rcQeL2ZfRSqdYg@mail.gmail.com>
To: Brandon Long <blong@fiction.net>
Cc: Bron Gondwana <brong@fastmailteam.com>, "dmarc@ietf.org" <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="001a114f4020faf23505571160d8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/dVlVF6F56yh6cz6GkJGqdsEWJ78>
Subject: Re: [dmarc-ietf] ARC-Seal is meaningless security theatre
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Aug 2017 01:43:59 -0000

On Thu, Aug 17, 2017 at 5:22 PM, Brandon Long <blong@fiction.net> wrote:

> We went down the path of including a diff of the message in the headers,
> but you run up against more complicated changes that make that
> challenging.  Ie, mailing lists which strip attachments.  If all we cared
> about were subject munging and footers, there probably would have been a
> practical solution there.
>

I wrote a draft a while ago that would allow a DKIM-Signature to include an
annotation indicating that the signing ADMD did one or more of a specific
set of small but well-defined message changes (e.g., add a footer, add a
Subject tag).  Knowing what those are, a verifier could undo them and
attempt validation of earlier signatures in the handling chain.  Presumably
if no other modifications were made, the original content is thus
discoverable, and you could then produce a chain of custody of the actual
content before you that makes sense.

If that's worthy of consideration now I could certainly revivify it.

-MSK