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

Bron Gondwana <brong@fastmailteam.com> Thu, 17 August 2017 01:48 UTC

Return-Path: <brong@fastmailteam.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 58BA9132416 for <dmarc@ietfa.amsl.com>; Wed, 16 Aug 2017 18:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level:
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=fastmailteam.com header.b=HUhR+ezm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=jnwqkfxg
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 e13UyAghQCFa for <dmarc@ietfa.amsl.com>; Wed, 16 Aug 2017 18:47:59 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3755C13241A for <dmarc@ietf.org>; Wed, 16 Aug 2017 18:47:59 -0700 (PDT)
Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id A7BDA20BE9 for <dmarc@ietf.org>; Wed, 16 Aug 2017 21:47:58 -0400 (EDT)
Received: from web5 ([10.202.2.215]) by compute6.internal (MEProxy); Wed, 16 Aug 2017 21:47:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=content-transfer-encoding:content-type:date :from:in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=JtCOLB9jtuLiuoIDh viLe7xyZkB63KiDrc2W2mAw3Jw=; b=HUhR+ezmZ3WlS+Zz7/xa+zHew1yj/9j/x wHmY0lXUff4ySHm0u1tialp6bLoJQE/kMJSMak5h8G9XoSJoVZx6MdKb3vG3dRfr DBBwNZN3mMC7u0Z+sFQg/mj3kJmh1U23RsugybP1wEcMgAJt9X2ruXR7RJV3K5rE xWNqTyPA9yd2YaMM3FwxUuRCgEEI/NptSvERg/v0AmHuMxpKkO+dxiaPd2OziK1E IwJjb+eEWEOEFYX9WVCBtZCPvu2Nwspa8Gya+LqZyLxLisIpwmIcBisLcgILVxyg QRMX+/dtdW/RSRopvwG/7UuLxoxIQN+pItxTWz08KQVSFT+tDYcDQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=JtCOLB 9jtuLiuoIDhviLe7xyZkB63KiDrc2W2mAw3Jw=; b=jnwqkfxgHYmUb1epybsL4j AmByH5bGA8mtSgTbV7Xt5F1tDFHtSsFjLjXKvYFuU/leC+eA8QfzrQAXtJy+n/jH 7hvScbDbpN/WQcg9u3aa0sCyCtLYL6gxM3rSS0amEVkaoCDuYYN6dq02vMgYBoRg DHXDG5ORsjg7N6jZRFU/kPsfrn1XWTCeO7oI4Df5hsLNuFSNM+0PecX4QBNePvuk BwmexfXqDHkMdoSQCb142V5I4oTb20TY/iU7waPfapvLLW+3jWmeUmC/sbgY1zUa ZFCIyqXrEgM3e4KldJljcFg9ejpihohpDJ+/zmG5PTI0kbgOuocJso5r8GFBfENg ==
X-ME-Sender: <xms:zvWUWe97UfqkAETQoY0fc5LBzRDJd0gHsbzgOMIBLQ8HpQmZayQkfQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 80CBA9E2B5; Wed, 16 Aug 2017 21:47:58 -0400 (EDT)
Message-Id: <1502934478.4053636.1075936440.4863007F@webmail.messagingengine.com>
From: Bron Gondwana <brong@fastmailteam.com>
To: dmarc@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_150293447840536360"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-42cf1507
In-Reply-To: <CAD2i3WMFpQzX-gGRfnPkKT+XrdiapDcjFpBqsy0CBEb+jwjMRA@mail.gmail.com>
Date: Thu, 17 Aug 2017 11:47:58 +1000
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> <CAD2i3WMFpQzX-gGRfnPkKT+XrdiapDcjFpBqsy0CBEb+jwjMRA@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/Y25enoI4fCs_-67fieiBolL4c6w>
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: Thu, 17 Aug 2017 01:48:05 -0000

On Thu, 17 Aug 2017, at 11:32, Seth Blank wrote:
> On Wed, Aug 16, 2017 at 5:47 PM, Bron Gondwana
> <brong@fastmailteam.com> wrote:>> While there exists A SINGLE SITE which is ARC-unaware and DMARC
>> p=reject aware, you can't use ARC on a DMARC p=reject domain without
>> rewriting the sender.  Otherwise that site will bounce the email.>> 
>> You still have to rewrite the sender until there is either full
>> adoption or sufficient adoption that you just don't care about the
>> stragglers.>> 
>> ARC doesn't solve that unless every receiver is either ARC-aware or
>> DMARC-unaware.  Hence the suggestion that I think Hector is making -
>> to define a new policy p=rejectnonarc or something, which means that
>> sites which are ARC-unaware accept rather than reject.> 
> So this is an excellent and crucial point that has been discussed
> again and again on and off this list.> 
> ARC only works if critical mass can be reached - both of
> intermediaries who break DKIM and receivers who evaluate ARC.> 
> Fundamentally, ARC will never reach critical mass if senders now also
> need to enter into the equation with an additional flag on their DMARC
> record. This is too high a bar and increases the interoperability
> problems as opposed to reducing them.> For now, there is a clear unanswered question: what coverage of
> receivers is needed for most mailing lists to achieve stable delivery
> once ARC is in the mix? Knowing the landscape of receiving domains, I
> believe this to be a small number. From the above comments, I'm
> guessing you think this is a large number. We're not going to resolve
> this difference of opinion in an open forum. However, releasing ARC as
> an experiment into the wild for major lists like the IETF and M3AAWG
> will give us very clear data very quickly on what the actual landscape
> looks like, and what ARC does and does not solve.> 
> In its current form, ARC only helps mail flows, it does not harm them.
> How effective this improvement is remains to be seen, but preliminary
> information I've been hearing about (which could be totally wrong)
> makes it seem like the improvements are dramatic. So let's get ARC
> tied off as an Experiment (thank you, Dave Crocker), collect some
> data, and see where things stand. Maybe things are great and ARC can
> move to proposed standard. Maybe it fundamentally needs more receivers
> in the mix than currently expected, and some fix for that is needed.
> But we'll know that after the experiment has begun, not before.
Seems reasonable.  We will deploy it at FastMail for sure and
collect data.
Bron.

--
  Bron Gondwana, CEO, FastMail Pty Ltd
  brong@fastmailteam.com