[openpgp] Re: text vs. binary in an OpenPGP "Signed Message"

Daniel Huigens <d.huigens@protonmail.com> Mon, 03 March 2025 10:43 UTC

Return-Path: <d.huigens@protonmail.com>
X-Original-To: openpgp@mail2.ietf.org
Delivered-To: openpgp@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AC23D586C19 for <openpgp@mail2.ietf.org>; Mon, 3 Mar 2025 02:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=protonmail.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wJ3hy3qXoX9H for <openpgp@mail2.ietf.org>; Mon, 3 Mar 2025 02:43:49 -0800 (PST)
Received: from mail-10631.protonmail.ch (mail-10631.protonmail.ch [79.135.106.31]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D3E35586C04 for <openpgp@ietf.org>; Mon, 3 Mar 2025 02:43:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1740998628; x=1741257828; bh=M1rllw+o0FxBn0FqbAdN32usqbIiXmJzCi7n+YwnKuM=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=nqTYyS3FbbedlaKu/CI6Ft60PsDm0Q3WbX0IyRBSPejElcNMzrbK2g9MrlgqSf67X x2mFAF5R9KsPnFYlq5EywsUOPIBFjUvHDXGs3wsZSnhLwOOuKatLHtH4ng1VT+OOAq fhHG8jdGEiZTnStTXxiZmcUU9DErq4d2S44HhhhdlBeCyLJp0JA1qV46glkUi5r4jg UaYB6nFagpOqNIKM2BKPjtCVJGoK22/aFeBfPpkIPN+JTzaLKLAxq3RL4zWQNNIzKz 4QGMmjW/7wPQ7hv60HaH7nHkvpXzDFXhnOeFE1x3kSJwBFu1IetQ4fUQ73Lh7fRJbL 6eW8vsqmqNC6g==
Date: Mon, 03 Mar 2025 10:43:42 +0000
To: Justus Winter <justus@sequoia-pgp.org>
From: Daniel Huigens <d.huigens@protonmail.com>
Message-ID: <euodfAz9Ixsk9-TgcVJf0uTIC9txOTgvznS9ADAh3UsulwBcv04x_i-TkTbdwRhe-uAyvpfqtxnXTgWw4PeM_4WsQeN_xumpcOrEft9ixg0=@protonmail.com>
In-Reply-To: <87o6yiigut.fsf@europ.lan>
References: <871pvq4yhe.fsf@fifthhorseman.net> <87o6yiigut.fsf@europ.lan>
Feedback-ID: 2934448:user:proton
X-Pm-Message-ID: 229b0467bae7c554e299ffa74f8defa4e5e4fe2d
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: 7S5273767KROSBYNOOBGPCOQNGPHUIY4
X-Message-ID-Hash: 7S5273767KROSBYNOOBGPCOQNGPHUIY4
X-MailFrom: d.huigens@protonmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-openpgp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, openpgp@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [openpgp] Re: text vs. binary in an OpenPGP "Signed Message"
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/soKwi6jI1F_K8TDla71vcfcnDzU>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Owner: <mailto:openpgp-owner@ietf.org>
List-Post: <mailto:openpgp@ietf.org>
List-Subscribe: <mailto:openpgp-join@ietf.org>
List-Unsubscribe: <mailto:openpgp-leave@ietf.org>

Hi :)

On Monday, March 3rd, 2025 at 10:49, Justus Winter wrote:
> > - If not, should a verifier that encounters (d) attempt to apply CRLF
> >   line endings to the LITb?
> 
> No.

I'm confused by either the answer or the question :')

When I answered yes, I meant, the verifier should normalize the line
endings of the contents of the literal data packet before feeding it
into the hash of the signature.

I agree that it shouldn't affect the data returned to the application.

Best,
Daniel