Re: [dmarc-ietf] WGLC ARC-16 concern on Section 5.1.2 - cv=fail should sign greedily

Seth Blank <seth@sethblank.com> Fri, 27 July 2018 17:29 UTC

Return-Path: <seth@sethblank.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 CA4CC130FA2 for <dmarc@ietfa.amsl.com>; Fri, 27 Jul 2018 10:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sethblank-com.20150623.gappssmtp.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 AQE2owlBFZVY for <dmarc@ietfa.amsl.com>; Fri, 27 Jul 2018 10:29:47 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (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 AC228130E8C for <dmarc@ietf.org>; Fri, 27 Jul 2018 10:29:47 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id k81-v6so10395141oib.4 for <dmarc@ietf.org>; Fri, 27 Jul 2018 10:29:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sethblank-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=W0nS4Ky8O+mgDTBVrxoCih6JLa4m/pH3boA+QPy0Ghg=; b=Cqgj/P4nKg/6MpGnNuAWA1JMdQpXcf/sRvV9kTYWVPJ6PW85KZ+ZAvLHKHSdhQPerz sT5XrCw4RN1YuvLGT0FoxnSrulICR/g9TXvFFecvVb79xVsPU+VZcerRGC855ZahrjM3 pzBguQ5JVEBMzToI5H0pyZO8gY6xJx8ojcQsMo65XBSr6IRWm9FSuV+uJyeB0/hov14T WdMlZ6X2JwAzIVQmMyT65kV1up/6Cvz9PMf+5ed4sIz4ICLFVzSL04kQoZYzIdQIvJsx hBv/hg4OLMhpobaiDDFMjgMawu0jxPEzPlAbZlyFf4ymxHTzTZ0B8erCaxpCyujbZ4Mv DMMA==
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; bh=W0nS4Ky8O+mgDTBVrxoCih6JLa4m/pH3boA+QPy0Ghg=; b=Npqx1BjSgrfBnP5X6wOjdrGv15sQs4opWBDIMvH+YrJnu3JXD0uxzr0xJZ9iqLrFKR Ii4iuzgJwJt9YXbDp/me07dILM5zLJ8hKpMpgMpvndl/pkeu92JItRFb5aevMHA0pAQm a2GEIavxue82GaqOWL6PM0nN0Ic2+XGRhdWjltx0wNeh0hQdsJ1J3V8wPwWhdcbJTvd7 ML66ParaI+bl/NO+4TREnFioA6ckzcu5Yg8Rt3qGWkRAE4QfX8DTL1eTwDOM5DVQJzZ2 kplM390kycbnfoj3zHGjZi5Sk2+M5xv9jQrvMkO9FUI+tRmBLVkXyT0DWUyLxzLi5SMW 78uw==
X-Gm-Message-State: AOUpUlG7KapRMNZKc3RO/rRJsDmHf0txg6tcNOmEBXNiSLrlbZKz4QAv zJh3Ghn5iJvem9aKh69mKuR0ndpA/wRTW8fJazRTPz9q
X-Google-Smtp-Source: AAOMgpdefok3LyrxBOEMtfzdmmlirmtMlqDeVNdOg9pMd8iHx/YYik/pDMbK5yFnV2UiHFyLlGF6/v9fiAIF4TycQME=
X-Received: by 2002:aca:3d05:: with SMTP id k5-v6mr6843806oia.86.1532712586540; Fri, 27 Jul 2018 10:29:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:2646:0:0:0:0:0 with HTTP; Fri, 27 Jul 2018 10:29:26 -0700 (PDT)
In-Reply-To: <CAL0qLwZ_uPh5iPkS7MKzDp3x=dAgn-hmsEunccDc3Hj2bsphpQ@mail.gmail.com>
References: <CAD2i3WMMJPaZYonS-qcz8pwOKYmS2Xe+8WBZPuAqjiGoYePzSg@mail.gmail.com> <CAL0qLwapyX3U=0OqQWzx+dDELn3W0v=N_HyzDnSw49oWQ+SE5Q@mail.gmail.com> <CAD2i3WN90JSS8pzgRxrbokuKmhZaLUrimYRWqkZwzVDBxTczng@mail.gmail.com> <CAL0qLwZ_uPh5iPkS7MKzDp3x=dAgn-hmsEunccDc3Hj2bsphpQ@mail.gmail.com>
From: Seth Blank <seth@sethblank.com>
Date: Fri, 27 Jul 2018 10:29:26 -0700
Message-ID: <CAD2i3WM99Yy6Y=BQE4dC=Ffm7J32My160Xdm2oxXC50Au9tXoA@mail.gmail.com>
To: IETF DMARC WG <dmarc@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004391820571fe75ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/kPGbLcL-0jGghtv6XUQgca-fGAU>
Subject: Re: [dmarc-ietf] WGLC ARC-16 concern on Section 5.1.2 - cv=fail should sign greedily
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 27 Jul 2018 17:29:51 -0000

On Fri, Jul 27, 2018 at 10:21 AM, Murray S. Kucherawy <superuser@gmail.com>
wrote:

> On Fri, Jul 27, 2018 at 8:35 AM, Seth Blank <seth@sethblank.com> wrote:
>
>> The verification algorithm is straightforward. If you receive a chain
>> that ends with cv=fail stop your evaluation, you’re done. There’s no
>> separate validation path here.
>>
>
> Then why bother signing anything when you affix "cv=fail"?
>

Because adding your ARC Seal over the chain guarantees that the receiver
has a complete list of everyone who modified the message up until the
failure. Without this signature any failures cannot be localized, and any
ARC data in a failed chain could not be trusted. This data is crucial for
analysis, understanding the experiment, and reporting back accurate and
untampered information.