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 22:08 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 7E6F7C151993 for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 14:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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_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 EQndiNRNPEGz for <ietf-dkim@ietfa.amsl.com>; Mon, 5 Feb 2024 14:08:44 -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 6BD1CC15198F for <ietf-dkim@ietf.org>; Mon, 5 Feb 2024 14:08:44 -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=UWrjsaVbbfkNgl8/aDWo0R61j4eXgRLJNEoawX5jy9Q=; b=j956BLLLENWL46tSBfHhdZPJ/s IR+f2KHyjrwcuwyR0cagYqDgYn7CrIkz3N3ixwnbwhRYH7dE/kzrQuuGvrR35Cj+AwOiavKx+04Ec PSym0xBuusGA6Y3lNJmTy9mrs8lH/52ulc6DgJmhfMU+f9TAv0kM36eQkJjbOLKb9j1Y=;
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 1rX78t-0001Uu-ER; Mon, 05 Feb 2024 14:08:43 -0800
From: Jim Fenton <fenton@bluepopcorn.net>
To: Dave Crocker <dcrocker@bbiw.net>
Cc: ietf-dkim@ietf.org
Date: Mon, 05 Feb 2024 14:08:42 -0800
X-Mailer: MailMate (1.14r5852)
Message-ID: <3E7A38EF-4026-4943-8BC3-22516E3F1C56@bluepopcorn.net>
In-Reply-To: <33756c23-7ff5-4ce1-a326-270155da4125@bbiw.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> <7035E051-7B4D-4CE1-A923-7BE59FC76195@bluepopcorn.net> <33756c23-7ff5-4ce1-a326-270155da4125@bbiw.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/RgxIbpH1SAhWCRloYbQe30sIAKM>
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 22:08:48 -0000

On 5 Feb 2024, at 14:02, Dave Crocker wrote:

> On 2/5/2024 1:56 PM, Jim Fenton wrote:
>> And you will also provide citations to refereed research about what you just asserted as well, yes?
>
>
> Ahh, you want me to prove the negative. That's not exactly how these things go.

You said that the URL lock symbol failed. Asking for research to back that up is not asking for you to prove the negative. I suspect there is research out there that backs up that statement, and I’m just asking for the same amount of rigor that you are asking for.

v2.23.0 | Report a Bug | By Email