Re: [dmarc-ietf] why ARC

John Levine <johnl@taugh.com> Sun, 14 June 2020 18:43 UTC

Return-Path: <johnl@iecc.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 B96073A0831 for <dmarc@ietfa.amsl.com>; Sun, 14 Jun 2020 11:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=pXeOK2Of; dkim=pass (1536-bit key) header.d=taugh.com header.b=MutWyMxb
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 7BXRPgoIQH9b for <dmarc@ietfa.amsl.com>; Sun, 14 Jun 2020 11:43:03 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E84253A0829 for <dmarc@ietf.org>; Sun, 14 Jun 2020 11:43:02 -0700 (PDT)
Received: (qmail 55531 invoked from network); 14 Jun 2020 18:43:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=d8db.5ee66fb4.k2006; bh=vKG7N+WJxr3bCse3ENl/0TOcLqp+740zQxyXk4cTgsY=; b=pXeOK2Of4Hr90qb5sn4HTsh/h9Bb5QzPEl9ucuC01sXXbdY9LtZsxBvoMHKk951LVfgzH6m2WQuqwqmekVN7mT4pSJJIlk4ExsmXyLypWV3+x3+ARLpLFhNml4lVI8W+zVcgZfPioe5swFuoIqmi95BkkxLQr3wyPf7UiM5TJQNKtP/Ei+yzeU2aryYBxrF2CkPtuGRT+2FvqJJMU47DkNcpvGBZvB72UqB3DynPSbtTyN+YopLzKS0O2wMcbBP2
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=d8db.5ee66fb4.k2006; bh=vKG7N+WJxr3bCse3ENl/0TOcLqp+740zQxyXk4cTgsY=; b=MutWyMxbfcVrP54gH4ucP/30hAWhfS38APrCaUwiGFSxVXC/R4zTO7Gr5oKGWP6gGegGc+/SvUQwny6zezxF+fhZwPEodx+/UOg1xKunDS++wVoYpzWb1CFS86Dub71s7lOe+yR1UbL05VQKKWUsRkS5K7+xuPpLh8CZXg0ckvHqKmku7lRGZ5FuOyqoSTxHZDPvavGYPXDig57qo5aVOPPVx4neqVyHw4uSMCO5aBEFMtfT7U/9FlcuyW+GcCao
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 14 Jun 2020 18:42:59 -0000
Received: by ary.qy (Postfix, from userid 501) id C22951AB79FE; Sun, 14 Jun 2020 14:42:59 -0400 (EDT)
Date: Sun, 14 Jun 2020 14:42:59 -0400
Message-Id: <20200614184259.C22951AB79FE@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: kboth@drkurt.com
In-Reply-To: <CABuGu1oVA-4w49+-6u_hyCbpJV39xZH0gHHdug2d1SoPWQeaMA@mail.gmail.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/gll_AD80SzysVJi9GDeKM12OslA>
Subject: Re: [dmarc-ietf] why ARC
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
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: Sun, 14 Jun 2020 18:43:05 -0000

In article <CABuGu1oVA-4w49+-6u_hyCbpJV39xZH0gHHdug2d1SoPWQeaMA@mail.gmail.com> you write:
>-=-=-=-=-=-
>> > ARC lets the recipient look back and retroactively do the filtering
>> > the list didn't.
>>
>> The concern about the creator of an ARC chain spoofing the purported
>> origin of a message is valid.
>
>By "creator" do you mean "initiator" (aka, the source of the first ARC set,
>i=1)?

I think it't the other way around. Let's say you get a message with
three ARC seals. For i=3 both the AMS and AS headers should validate,
since the message came directly from the entity that put on that seal.
For i=1 and i=2 the AS should validate but the AMS probably won't. The
cv= tag in each AS header tells us whether the AMS was good when it
arrived at that intermediary, so the i=1 and i=2 seals are only as
good as the i=3 signer's reputation.

I were a certain kind of bad guy, I would take the two seal ARC chain
from a message from a virtuous sender, replace the message body and
>From and Subject line with my spam, add a fresh new i=3 seal and blast
it out. That ARC chain is 100% valid, even though the messsage is
spam.

That's why (as Kurt knows) you only pay attention to ARC seals from
senders that are otherwise credible.

-- 
Regards,
John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly