IETF Logo Mail Archive

Re: [Ietf-dkim] Headers that should not be automatically oversigned in a DKIM signature?

Jim Fenton <fenton@bluepopcorn.net> Mon, 05 February 2024 21:57 UTC

Return-Path: <fenton@bluepopcorn.net>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFCE3C14F60A for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 13:57:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bluepopcorn.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nVMMNAR_H1ns for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 13:56:56 -0800 (PST)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BEFA1C14F604 for <ietf-dkim@ietf.org>; Mon, 5 Feb 2024 13:56:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bluepopcorn.net; s=supersize; h=Content-Transfer-Encoding:Content-Type: MIME-Version:References:In-Reply-To:Message-ID:Date:Subject:Cc:To:From:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=GOpO5z4AB6aLOPxqY67u04Tcd+TK3o36VmaF//qD9xk=; b=jTYMcqgC6LsuMN5rGG7vjDoaYA JqcqETI57YbBj8A30n2BQcCuBDGGCg8+FdChwOM6WMc9APY7XzhEOA153Wsvkqd4JYichdAzHeSwW Uhl15jtqlxJgVGIzy1jWSbV+Z+I1GjPTvksE0YprsKh3vyi2P/2r5d2L+gsP7PSvlyIU=;
Received: from [12.89.238.34] (helo=[10.100.9.254]) by v2.bluepopcorn.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <fenton@bluepopcorn.net>) id 1rX6xT-0001S7-Hz; Mon, 05 Feb 2024 13:56:55 -0800
From: Jim Fenton <fenton@bluepopcorn.net>
To: dcrocker@bbiw.net
Cc: ietf-dkim@ietf.org
Date: Mon, 05 Feb 2024 13:56:55 -0800
X-Mailer: MailMate (1.14r5852)
Message-ID: <7035E051-7B4D-4CE1-A923-7BE59FC76195@bluepopcorn.net>
In-Reply-To: <1c0a74ed-9366-4e11-9604-eab211a17046@dcrocker.net>
References: <20240119192026.DEDFF810437D@ary.qy> <20240120000053.FrDLzS4U@steffen%sdaoden.eu> <3f72e0c3-d245-16f7-57b2-831bfa53efbd@taugh.com> <4F161749-91D6-4E2D-AF70-89C5F172B971@isdg.net> <64f0cfd3-9d86-4d5e-b213-d0e53972c65a@tana.it> <af70d974-b2cb-4ac3-af9f-f0461238ebbb@isdg.net> <0cb52576-67af-4248-9866-5d2e2ef1adfd@tana.it> <8EA4F7EB-CBAF-4CBA-AD3B-03ECC8B05172@isdg.net> <012291f4-5098-4e6b-b9b9-a7e1fd681138@tana.it> <e59bbaa2-945c-4ed8-85b4-3a79ebc8bfbd@dcrocker.net> <20240205212412.Kq4PkTNC@steffen%sdaoden.eu> <1c0a74ed-9366-4e11-9604-eab211a17046@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/J6jx_iSacyJ4V3MifdTyInj_HfQ>
Subject: Re: [Ietf-dkim] Headers that should not be automatically oversigned in a DKIM signature?
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2024 21:57:01 -0000

On 5 Feb 2024, at 13:46, Dave Crocker wrote:

> On 2/5/2024 1:24 PM, Steffen Nurpmeso wrote:
>> I*totally*  disagree.
>> It is also a matter of education.
>
> Yeah.  No.  The standard example is the failure of the URL lock symbol.
>
> But given your certitude, please provide refereed research about persistent behavioral change from email header security-related information.

And you will also provide citations to refereed research about what you just asserted as well, yes?

v2.23.0 | Report a Bug | By Email