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

Dave Crocker <dcrocker@gmail.com> Sat, 12 August 2017 00:04 UTC

Return-Path: <dcrocker@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 BC5BC132459 for <dmarc@ietfa.amsl.com>; Fri, 11 Aug 2017 17:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 q9qYpc-bVDho for <dmarc@ietfa.amsl.com>; Fri, 11 Aug 2017 17:04:49 -0700 (PDT)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (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 F252C132465 for <dmarc@ietf.org>; Fri, 11 Aug 2017 17:04:48 -0700 (PDT)
Received: by mail-oi0-x22f.google.com with SMTP id x3so46657364oia.1 for <dmarc@ietf.org>; Fri, 11 Aug 2017 17:04:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=5M9TP1u5DoKasCttRoDxtEkUR1b052f6f5j1dCT5aPA=; b=f7ElNO0qnQJxhLmx+Ar3x3Xw1c+/AWfFSqUqNPFEEHjbMXRGcm3eQKxM/yKCAsx2fq fAnBgXt0qsnZbtLfJkUd6nMHLdShi5YQ7bNYbJ/I/9EcOWq5Hg9OqTMH327onndsZasu xFAqOb0v9Pf4zeUxc1zBahxq7LFkE9GJaSqtRJEpLkp8Zy1+w7QAww217oQZuZAyrB4Q +cBQLTHlXn8HLp4bpGNBRnk4UmomTdPcRU6O5EIZrnR6VYF7LMY48MA/wxYcN4D1faaA ahRzGGxcPBJ9phl0y5ew+KpuwDjwzEoRt3ERRLgg4ZKJB6fn8iay/tqZ+bDxvoRt3NJk tPEw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=5M9TP1u5DoKasCttRoDxtEkUR1b052f6f5j1dCT5aPA=; b=DK3azv5UO+2hi/md/dEG/SrQY24xi1tqsX/cUDJwbITapYmP3GEjr+sz4WC8e3N8NZ VCZenHpkgmSs/PiPtpjBHnTrg8WS3rPT4WRb1pocuT1fuGA9woDnHPxYpckzt1qBmP47 a6D6UBwkVaHtkj9WnNGIhJsWIiqx4WBFd3Dr8ObArcMgFnfKLdB1x/f3Oym/KTGzOVdd o/12AsoHrHZM0329XJDlllilSoK5HLg3ab3LEy9NUKQHdpEb9nlfFKgvgFhbYwyn4Frn nuuaJ9SEFNkmaACoVnRLCRnb+EncPN16lkYagy9rASR0k8FK/F9KQeVVg3tZLnGtUeEb FsOQ==
X-Gm-Message-State: AHYfb5jj9nnInXwm7hzNoWgZUkLI/REFhUYMrf1jVQNxOiHMXHXcwoP+ PU+gHfWnRAeOgR//0c8=
X-Received: by 10.202.74.22 with SMTP id x22mr18157861oia.254.1502496288064; Fri, 11 Aug 2017 17:04:48 -0700 (PDT)
Received: from ?IPv6:2602:304:cda0:8800:d17e:7fe3:9cb7:7c98? ([2602:304:cda0:8800:d17e:7fe3:9cb7:7c98]) by smtp.gmail.com with ESMTPSA id a6sm2579919oic.10.2017.08.11.17.04.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Aug 2017 17:04:47 -0700 (PDT)
To: Bron Gondwana <brong@fastmailteam.com>, dmarc@ietf.org
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>
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <166070f0-4ba1-70da-1f73-885b4a7f7640@gmail.com>
Date: Fri, 11 Aug 2017 17:04:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <1502495646.4099176.1070896040.2B09B1F8@webmail.messagingengine.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/0tZofKIiSYzUJb5RCtpW5Nr1tdo>
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, 12 Aug 2017 00:04:51 -0000

On 8/11/2017 4:54 PM, Bron Gondwana wrote:
> On Sat, 12 Aug 2017, at 03:22, Dave Crocker wrote:
> 
> I'm just picking out the key quote here:
> 
>> On 8/7/2017 4:22 PM, Seth Blank wrote:
>>
>>     When validating an ARC signed message, one verifies the latest AMS
>>     (which must validate), and *the entire chain* of ARC Seals, not only
>>     the latest. This guarantees you a list of all message signatories -
>>     the chain of custody we're talking about.
> 
> Yes, I follow this bit, but then...
> 
>>     When evaluating the chain for final receipt, there are two states to
>>     worry about as a matter of local policy: 1) you trust all the
>>     signatories on the chain 2) there is an untrusted signatory on the
>>     chain
> 
> Which is why it's a bad idea to sign if you're not modifying, because 
> then everybody has to trust you or their chain breaks, even though you 
> didn't do anything which required signing.

I don't have an opinion about whether this conclusion is correct, but 
I'm quite certain it a type of consideration that needs to be 
fundamental, to recommendations about usage.  Who should do what, and 
why?  What are the upsides of their doing or not?  Downsides?



>>     Without the ARC Seal this determination is not possible and there is
>>     no way to evaluate the ARC chain for delivery as a final receiver.
> 
> And this is the crux of our disagreement.  Seth thinks it's necessary to 
> do more than signing a statement that you believed the message was 
> authenticated when you got it, in a way that the next hop can verify 
> your signature over your own Authentication Results plus the content of 
> the message.  I disagree.
> 
> I'm proposing exactly the same stragety DKIM uses, just with series of 
> signed "chain of custody" statements rather than the DKIM signature 
> having to align with the sender domain.

by 'strategy DKIM uses' what do you mean exactly?  I'm guessing you mean 
having the signature cover more of the header and all of the body, but 
please confirm or clarify.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net