Re: [openpgp] Signing of literal data packet [was: Re: Disadvantages of Salted Signatures]

Werner Koch <wk@gnupg.org> Fri, 29 December 2023 17:37 UTC

Return-Path: <prvs=0727f13616=wk@gnupg.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02C58C14F60B for <openpgp@ietfa.amsl.com>; Fri, 29 Dec 2023 09:37:41 -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=gnupg.org
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 h7uQyxpP6BSM for <openpgp@ietfa.amsl.com>; Fri, 29 Dec 2023 09:37:35 -0800 (PST)
Received: from ellsberg.gnupg.com (ellsberg.gnupg.com [IPv6:2a01:4f8:151:7306::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 D2C16C14F5F2 for <openpgp@ietf.org>; Fri, 29 Dec 2023 09:37:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnupg.org; s=20181017; h=Content-Type:MIME-Version:Message-ID:Date:References: In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: 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=IHefcUS3BhukNT0t5mnrTUfQudY4U+iwJCiddaHlPdA=; b=C1JjqaSohXDBhW9EsQZzj7b8KB L2EBXtvuHJTPaswQieuZIPim2pdZBM+5Cj4BCaNfBixaahgJ3TWQAObmDWcFVAXzH+wm6E5YdKV+f yKNgjMszt7FVA/KjXvewNfS1iDbX970xDGtMEsoevNiX7lmWOa8Moen2yUWKHMCYwxpk=;
Received: from uucp by ellsberg.gnupg.com with local-rmail (Exim 4.94.2 (Devuan)) (envelope-from <wk@gnupg.org>) id 1rJGnc-0001oD-VD for <openpgp@ietf.org>; Fri, 29 Dec 2023 18:37:32 +0100
Received: from wk by jacob.g10code.de with local (Exim 4.96 (Devuan)) (envelope-from <wk@gnupg.org>) id 1rJGnv-0002L2-38; Fri, 29 Dec 2023 18:37:51 +0100
From: Werner Koch <wk@gnupg.org>
To: Heiko Schäfer <heiko.schaefer@posteo.de>
Cc: openpgp@ietf.org
In-Reply-To: <b63b70c4-a9e9-431d-b6e1-8eac70ae965b@posteo.de> ("Heiko Schäfer"'s message of "Wed, 27 Dec 2023 02:26:36 +0000")
References: <077dd27cef0c7d3968967fc4c3a880081b8bd9dd.camel@posteo.de> <87jzplrtfy.wl-neal@walfield.org> <87bd4895386b3a0cd0c62429b0b85df6f1860da2.camel@posteo.de> <db25c5b9-0d08-4b45-85c9-49b8277d80ec@gmail.com> <875y13sooh.wl-neal@walfield.org> <ba75b1b3-2b57-440e-ba6e-e9629bc9cf6b@gmail.com> <FF2CBF7A-8228-4483-9B43-B750ACBCE22F@riseup.net> <0cf9a740-d783-45c0-aa90-1d6868134021@gmail.com> <87edfp8d33.fsf@jacob.g10code.de> <b63b70c4-a9e9-431d-b6e1-8eac70ae965b@posteo.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Jabber-ID: wk@jabber.gnupg.org
Mail-Followup-To: Heiko Schäfer <heiko.schaefer@posteo.de>, openpgp@ietf.org
Date: Fri, 29 Dec 2023 18:37:45 +0100
Message-ID: <871qb46hau.fsf@jacob.g10code.de>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=cryptanalysis_Crypto_AG_Tuberculosis_Oratory_Symptoms_ISA_Iris_SAR=."; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/waKx4q71b9gJidQtNlbkX-_tm1w>
Subject: Re: [openpgp] Signing of literal data packet [was: Re: Disadvantages of Salted Signatures]
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Dec 2023 17:37:41 -0000

On Wed, 27 Dec 2023 02:26, Heiko Schäfer said:

> I'm surprised to read you "had to give up" dealing with that aspect of
> crypto refresh. My understanding is that signing of literal data
> packets in the crypto refresh text works *exactly* the same as in RFC
> 4880

Right, and this means that it does not fix the long standing bug that
the creation date, mode, and filename was not signed.  In LibrePGP
(i.e. rfc4880bis/crypto-refresh up to summer 2021) this was fixed.


Shalom-Salam,

   Werner

-- 
The pioneers of a warless world are the youth that
refuse military service.             - A. Einstein