IETF Logo Mail Archive

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

Dave Crocker <dhc@dcrocker.net> Sat, 03 February 2024 19:39 UTC

Return-Path: <dhc@dcrocker.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 CABDCC14F689 for <ietf-dkim@ietfa.amsl.com>; Sat, 3 Feb 2024 11:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 (2048-bit key) header.d=dcrocker.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 R27JH_3btP5f for <ietf-dkim@ietfa.amsl.com>; Sat, 3 Feb 2024 11:39:51 -0800 (PST)
Received: from iguana.tulip.relay.mailchannels.net (iguana.tulip.relay.mailchannels.net [23.83.218.253]) (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 48CE1C14F5F6 for <ietf-dkim@ietf.org>; Sat, 3 Feb 2024 11:39:50 -0800 (PST)
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 642708004DF for <ietf-dkim@ietf.org>; Sat, 3 Feb 2024 19:39:50 +0000 (UTC)
Received: from fr-int-smtpout4.hostinger.io (unknown [127.0.0.6]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id 932118012E1 for <ietf-dkim@ietf.org>; Sat, 3 Feb 2024 19:39:49 +0000 (UTC)
ARC-Seal: i=1; s=arc-2022; d=mailchannels.net; t=1706989189; a=rsa-sha256; cv=none; b=1+00mpLzLt4xIx657KmjwptFi2jBCCYjTa2sqbR03pQeKnErsV8W0mGO6Hqp0IG95yjbYK 0mLmpSDqMLhOp0E0gar+8vkaNzieYXd5+0Ky9zuIpLyIfSuFn4s8fqU0fy8TyZv1hDsxWn RheuKstRyjBKJY7/Mhqum4Wu9P2TqWnbcGKQs/12HignvTshjGLyqo0n/g1pYnXP6R3uDi FK4llSYLkZnmPqdMLRkfJk2RyT2wekqEJz3Ce2YxhEfxve4AniwJtK6uUkaC46Z4u/dOx/ 6D1G+Whir6B+QDPJeae2tXDDKV4zlnE6osUgR+ZryC/qMj6HCf6KQylHXgY8XA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=mailchannels.net; s=arc-2022; t=1706989189; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=yG/BnoR9/S0yO3/W7K/BAwTCooU7GOcNymMCF9VvumQ=; b=uXSyLztzSXiV1ay8V3/tDBLDJNCUL9EppN9BwiiQAHmembTJKu3BLAX8/W/RETPIlojVmI RDxGyiG5/cLyoXLFbjd4P+mYfpFjUQSBHM5KySop0iBJR1y/ZA/8RPhmDZ7Mck4UqIb3TL pDxkiLhb5XEgrdoaqwat3/wt25IVxuB+UZ43wKo5gH8oY0DEn9bPTBxosyVvrTEZS81Moj 3CZgdVV1hT+7V0gOlTQLcljY0zWdrj12pNSolJEqxlA41gcFDOwDGT/RzL4Qe1MT/dpZXi RJfVDT/qYDxQV8su4bDTqfbI9+2JD7kp29JWLl+4Fdb4nhzYm/0q5HjvV+yPpw==
ARC-Authentication-Results: i=1; rspamd-55b4bfd7cb-qggvv; auth=pass smtp.auth=hostingeremail smtp.mailfrom=dhc@dcrocker.net
X-Sender-Id: hostingeremail|x-authuser|dhc@dcrocker.net
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authuser|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Chief-Spot: 258d3bf2166816e4_1706989190124_2466014176
X-MC-Loop-Signature: 1706989190124:849013510
X-MC-Ingress-Time: 1706989190124
Received: from fr-int-smtpout4.hostinger.io (fr-int-smtpout4.hostinger.io [89.116.146.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.126.230.231 (trex/6.9.2); Sat, 03 Feb 2024 19:39:50 +0000
Message-ID: <117c5879-7255-43cb-bfee-2ca9413be4d5@dcrocker.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcrocker.net; s=hostingermail-a; t=1706989187; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yG/BnoR9/S0yO3/W7K/BAwTCooU7GOcNymMCF9VvumQ=; b=T0lRQVAiXXxIJ4vpQ7dA2kB4iRdd5DnFIV22d3ROxwd7yY6hKeVcRA1D8HOEm2kWVpJS8l ZQcf1F3Yw+1uKraGO6i+/sv1YoOpLdIPupS+tID4igJP0VxttDXpS8FRE7V/Foi3o5WLky AftoEPNgBph0PhC08BcCoor5X2StV5JUaHMBcUwU/ZGC3QOATPX1DrkG/o1O0uDdO//Z96 TC3i1WkJNHKrl4GTKDFDxde2lnt7f61d3DxiUwzdhZtTvcFGhETDJvAXIAULIg2n1Yytn5 2f0fUBmQAhjyRj0FW0LT78NKWVQjAuaunlHqn7WyYYPIrkxwAfG7kLxrIsPLtw==
Date: Sat, 03 Feb 2024 11:39:47 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
From: Dave Crocker <dhc@dcrocker.net>
To: John R Levine <johnl@taugh.com>
Cc: ietf-dkim@ietf.org
References: <20240202043446.AAF26820F0AD@ary.qy> <52b5c2f3-e52f-403f-becf-813bbaf7b870@bbiw.net> <479a6ba4-db35-0305-a1bb-03dc1c9ec722@taugh.com> <46b0e4e6-898a-4ab3-a51c-cc54abb14891@bbiw.net>
Reply-To: dcrocker@bbiw.net
Organization: Brandenburg InternetWorking
In-Reply-To: <46b0e4e6-898a-4ab3-a51c-cc54abb14891@bbiw.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-CM-Envelope: MS4xfPKxHzmY0yLzwuN8ldP6627Oq9tCAE6atW3uvzg+N5zSpRWvf4qwLF3ROjlTr1VNb4O0+Ee201nXpF6z+PRqiK6eL2vXB0VMvHWWm4rBtyWpGzfqXPWP kMqGhca40FsElpm1S/uK9678bG0kYRm7F+fHCbHSpM/TCex4PEHPt+jnGhy5D1JExBRDYXny/n+EGbltczVw6OneIMuCcSS7MdQ=
X-CM-Analysis: v=2.4 cv=HqBwGVTS c=1 sm=1 tr=0 ts=65be9683 a=f+oD5hTMMv8HtluUlp4ziA==:117 a=f+oD5hTMMv8HtluUlp4ziA==:17 a=IkcTkHD0fZMA:10 a=k7Ga1wGzAAAA:8 a=r1k-pTeS5xmEj6mxWJgA:9 a=QEXdDO2ut3YA:10 a=ijMaxGghyylP-n2pFjDB:22
X-AuthUser: dhc@dcrocker.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/y-G6F_pJCvbYvolTUEYfvx6zLmk>
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 19:39:55 -0000

On 2/3/2024 11:29 AM, Dave Crocker wrote:
> DKIM is not a general message parsing engine

btw, one might imagine a parsing engine that mixes a number of 
functions, such as general message parsing AND DKIM validation.

For such an engine, where a bare CR or bare LF might be illegal -- 
though it now appears they aren't -- the error to raise is for the 
general message processing, not for DKIM.

This nicely demonstrates the importance of distinguishing between the 
abstractions needed for public networking specifications, from various 
local implementation choices a programmer might make.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net
mast:@dcrocker@mastodon.social

v2.23.0 | Report a Bug | By Email