IETF Logo Mail Archive

Re: [Ietf-dkim] Question about lone CR / LF

John R Levine <johnl@taugh.com> Sat, 03 February 2024 18:32 UTC

Return-Path: <johnl@taugh.com>
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 EC1D6C1654FE for <ietf-dkim@ietfa.amsl.com>; Sat, 3 Feb 2024 10:32:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.408
X-Spam-Level:
X-Spam-Status: No, score=-4.408 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_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 (2048-bit key) header.d=iecc.com header.b="grZQG51b"; dkim=pass (2048-bit key) header.d=taugh.com header.b="MMqC9jkS"
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 Ga1XeicUYXlK for <ietf-dkim@ietfa.amsl.com>; Sat, 3 Feb 2024 10:32:09 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8082C15793F for <ietf-dkim@ietf.org>; Sat, 3 Feb 2024 10:32:08 -0800 (PST)
Received: (qmail 22899 invoked from network); 3 Feb 2024 18:32:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=597165be86a6.k2402; bh=lTa2dKMZ3QhDhpGRiOob8P9F0pNIzP3uNayDpO7lfRA=; b=grZQG51bQT/9peywv/2zlA9P+kzuHZGsSnB+mc8xndvKeH241SMRuDNy9zpBtY59rINrpAaOQRHmVFguRVt+t6vVFo9DwUc6UTK9vL/nFplQDgwH6jVRJ85NuDGuDK/6ClfPmC5bbqM9WxKtJtl18m55WE5SiRZo0SacjCFp0/ILe1jvF5TMRhLOALeFZPB7aysxRw9YJg/+xm1l7mEK6fkfKKhPtGnwMyaMIJAWxINzZqDK67fRZUSmh7CCh/Mx59pL61iiNahfwz/sj5Cz4HWB11vk0+21hFdx8weggduEdwXhDI6mfSxkEW52nXSSTyHJu7BBYOeo2vTvX6wUVg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type; s=597165be86a6.k2402; bh=lTa2dKMZ3QhDhpGRiOob8P9F0pNIzP3uNayDpO7lfRA=; b=MMqC9jkSjGx17U2qg8FdhYrlPZOm4njIp/pMp+RbFxc5bFDXy5gBi/vAytcdsyX8RUqunmIpB0VpKcPLWQyvWL8vSQus3xl09wNUgXUZyE3OLN+pcGr99pk3M4YYsLrGfh9lRz7ZPUCKC52ij/YKEevMtqMF5jhSD3TfHBM2HrbAi/yZybksSacIrtfDUMDC+YxK3WplBIP82mR58ngKF5Rhn1w4MbN4Ps9fcVU2IHFJWD1isGLNY/oo1ff5g1IAr4Ejx0hcJNmTMCO9zstdaEix9MOXEJiVYb/gGal0+P+1a6exmW6ZfED2JNud7bpk1aiI35g+n1FBQje5D77z/Q==
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 ESMTPS (TLS1.3 ECDHE-RSA CHACHA20-POLY1305 AEAD) via TCP6; 03 Feb 2024 18:32:06 -0000
Received: by ary.qy (Postfix, from userid 501) id E9B588227DF7; Sat, 3 Feb 2024 13:32:05 -0500 (EST)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 5086A8227DD9; Sat, 3 Feb 2024 13:32:05 -0500 (EST)
Date: Sat, 03 Feb 2024 13:32:05 -0500
Message-ID: <479a6ba4-db35-0305-a1bb-03dc1c9ec722@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Dave Crocker <dcrocker@bbiw.net>
Cc: ietf-dkim@ietf.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <52b5c2f3-e52f-403f-becf-813bbaf7b870@bbiw.net>
References: <20240202043446.AAF26820F0AD@ary.qy> <52b5c2f3-e52f-403f-becf-813bbaf7b870@bbiw.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/_bYBS9XAMeYKmZLPpFegBmE9mI4>
Subject: Re: [Ietf-dkim] Question about lone CR / LF
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: Sat, 03 Feb 2024 18:32:14 -0000

On Sat, 3 Feb 2024, Dave Crocker wrote:
> Having a DKIM module check for one aspect of RFC5322 conformance raises a 
> need to make it a full RFC5322 compliance engine.

That's easy: no, it doesn't.

Any DKIM signer or verifier already has a state machine looking for CR and 
LF to do header or body canonicalization.  When the state machine runs 
into a bare CR or LF, it has to do something.  The only options are to 
produce a wrong result, since there is no correct result, or no result. 
(As I said in a recent note to Murray, which wrong result is likely to 
vary depending on local file details.)  You seem to be saying that as a 
matter of principle it should produce a wrong result.  I'd rather not.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

v2.23.0 | Report a Bug | By Email