Re: [dmarc-ietf] Response to a claim in draft-crocker-dmarc-author-00 security considerations

Dave Crocker <dcrocker@gmail.com> Sun, 19 July 2020 15:13 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 69AC33A096B for <dmarc@ietfa.amsl.com>; Sun, 19 Jul 2020 08:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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 tkExI_HSetVc for <dmarc@ietfa.amsl.com>; Sun, 19 Jul 2020 08:13:21 -0700 (PDT)
Received: from mail-oi1-x233.google.com (mail-oi1-x233.google.com [IPv6:2607:f8b0:4864:20::233]) (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 5665F3A0967 for <dmarc@ietf.org>; Sun, 19 Jul 2020 08:13:21 -0700 (PDT)
Received: by mail-oi1-x233.google.com with SMTP id j11so12363472oiw.12 for <dmarc@ietf.org>; Sun, 19 Jul 2020 08:13:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=ErnrGwaYSKvFR2uHqmHcfOTe5elFNFvlmhKfYHP/68k=; b=tg9B2jeeI1inqc8VECgMnvJU36TSCJ67q7h3ZwtQ+H31WQBi8SKRjMraGWBneJOLRX BFyRkEaW/5ti5qsxtBsx8QwwfOBJUH4FPGuYwcNIOM8EYdTmAgCOGXuQO6k09phH1Aud OSxdn+2+KJe1AegiDuwdUJgr+s5QxfdcBkSjgZD6LPa9uTYBYzr4kiJ4iQqBjLqVm4hY iZwyI7cjhCEDi9zcNmDyilAImdwPFSpzuxLGH89w/zBzEeqkLA7v1ybG71B5QN+nCo8D XhkEnsjvPA1a9TXzOtjNMMfa9oXf7l94+J9nYiLbqpKfjSZDAU8rsl8FopcF6oTOkp08 4vLw==
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:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=ErnrGwaYSKvFR2uHqmHcfOTe5elFNFvlmhKfYHP/68k=; b=oH6j8DBZK3wNDMO2Xt6IngbT0hu6jVDnNrvStqqPSs9Yjrj9MYRG2UoAVKghi7PD/t Iiw1cDLEv1fdMea+x+AvuPlbsrsVvlrbWj8D6JaLILESMRE60PvVmISg6oGXIT4IeIfZ AugoDEraDQGrBOwO3HN9Z2/Q0cxFOqgZ4q5F8qvy2Odcwe6rte3qFXNhOYc2QL7UKh5m fAUBlMoMBTXQwcs9GK5i+pORudOseYvD4oF32xSRs16/fkrHWdRFR4oQHPiuOO+DLEKg 8Zx9tXsNHttEvzm4hOp33Oi6KTljEFi27hWxjEONa3Y0eDt3AtY+15ZnPWJvBShEeptX XNSw==
X-Gm-Message-State: AOAM532fmpsG85Aqd7bt517vAO/7WnIn6/+0s8kTeDi9q64+YBgfO5Tq QkljXhIl21eeE4grPEWnMsNkVdaqGrw=
X-Google-Smtp-Source: ABdhPJyv7+G42v/ZcYwOf0FaUWU1KZerLKXmt36kN+6OBgAYJosFEPtjNom6sRIeKCGS7+tAtT8o3A==
X-Received: by 2002:aca:1016:: with SMTP id 22mr14016780oiq.66.1595171600499; Sun, 19 Jul 2020 08:13:20 -0700 (PDT)
Received: from ?IPv6:2600:1700:a3a0:4c80:fc69:4fcf:5c0d:166? ([2600:1700:a3a0:4c80:fc69:4fcf:5c0d:166]) by smtp.gmail.com with ESMTPSA id n141sm3463077oig.24.2020.07.19.08.13.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 19 Jul 2020 08:13:20 -0700 (PDT)
To: John Levine <johnl@taugh.com>
References: <cd9258e6-3917-2380-dd9b-66d74f3a64d3@gmail.com> <20200717210053.674D61D2C431@ary.qy> <CAL0qLwbkhG-qUyGqxaEjcFn2Lb7wPMhcPFEMA8eqptBJpePPxA@mail.gmail.com> <0bbf7999-0b40-401f-24d0-09eb1c8ec2d4@gmail.com> <rf1nkv$1hj6$1@gal.iecc.com>
Cc: dmarc@ietf.org
From: Dave Crocker <dcrocker@gmail.com>
Message-ID: <6eeee2ed-1112-335c-6bc2-b426de97f709@gmail.com>
Date: Sun, 19 Jul 2020 08:13:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <rf1nkv$1hj6$1@gal.iecc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/YwZE5prZjfhITGlV5Bxw-xMw11U>
Subject: Re: [dmarc-ietf] Response to a claim in draft-crocker-dmarc-author-00 security considerations
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, 19 Jul 2020 15:13:22 -0000

On 7/19/2020 8:08 AM, John Levine wrote:
> This tells us that at least at one big gorilla, the header address
> isn't something that users see.  This leads to two questions, one being
> why the From address is a better authentication handle than, say, DKIM d=.


I think the possibility of d= hasn't been considered seriously. I'm not 
going advocate, but it's worth thinking about this a bit, just to make 
sure we understand it's implications.

I've thought (assumed, recall) that From: was chosen because it is the 
only address value in email that is required to be present.  So it gives 
you a domain name to start from and then look up for a DMARC record.

There is always that domain name, even when there is no authentication 
information.

It's only possible to use the d= if there is a signature.  So a 
downgrade attack would succeed by merely removing the DKIM information.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net