IETF Logo Mail Archive

Re: [openpgp] To bind or not to bind

Justus Winter <justus@sequoia-pgp.org> Sat, 23 March 2024 11:28 UTC

Return-Path: <justus@sequoia-pgp.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 2E5B9C14F693 for <openpgp@ietfa.amsl.com>; Sat, 23 Mar 2024 04:28:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_HI=-5, 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 (4096-bit key) header.d=sequoia-pgp.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 hcJNCkhju2GE for <openpgp@ietfa.amsl.com>; Sat, 23 Mar 2024 04:28:26 -0700 (PDT)
Received: from harrington.uberspace.de (harrington.uberspace.de [185.26.156.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 966AEC14EB19 for <openpgp@ietf.org>; Sat, 23 Mar 2024 04:28:24 -0700 (PDT)
Received: (qmail 14583 invoked by uid 500); 23 Mar 2024 11:28:22 -0000
Authentication-Results: harrington.uberspace.de; auth=pass (plain)
Received: from unknown (HELO unkown) (::1) by harrington.uberspace.de (Haraka/3.0.1) with ESMTPSA; Sat, 23 Mar 2024 12:28:22 +0100
From: Justus Winter <justus@sequoia-pgp.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, Aron Wussler <aron@wussler.it>, "openpgp@ietf.org" <openpgp@ietf.org>
In-Reply-To: <871q814nlz.fsf@fifthhorseman.net>
References: <EGivTgyfjNm_TAvhds1OPA2c0O6LP9lFnkwWHHKLJY8ReJOgtDh3tnYsCSR8yrrBLbpeehtUgIJEhynae8L3daRimNiGO7BAb3cVvC66q-4=@wussler.it> <87a5mqi0xi.fsf@europ.lan> <871q814nlz.fsf@fifthhorseman.net>
Date: Sat, 23 Mar 2024 12:28:15 +0100
Message-ID: <877chti3w0.fsf@europ.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
X-Rspamd-Bar: -----
X-Rspamd-Report: BAYES_HAM(-2.996339) SIGNED_PGP(-2) MIME_GOOD(-0.2)
X-Rspamd-Score: -5.196339
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sequoia-pgp.org; s=uberspace; h=from:to:subject:date; bh=7uon7cEFMudQB6gwIO3mc3PFQ6cgUFBkSQy8Y8CuA1Q=; b=A/mHff5myN68BGwWsvpeMWMqSv44FL42haKlzh4gIfwLb+zPph4OP1sx/6U6et2ZgoFf3EAe7v xeFLP4366vAd/ZlNgmM5umOp+Up92v0bmaWPIhVfZq4VeZqufNCSrIU81lOqqKzksBxTkq2Yo9uv oRJ6BgJURwmRukpQln9DbdcIxz3vghFLoH8B7WF5vHIu9Cl58H5wcIasoWebsPyHKWEh0n3clblE WZyywPsucbzE7IJ88n6ensnJ9p7/ItbISKz0X4kd3pdNYwnhQdWUpsVv5CfYHjQ/gip4ibtA7kJx XlXmJaleV1oRsnviPjAfCV+zKjqFj7jqR+ZoURlO+YxA7WiFNHHorFWTyV/IU2JeJinCKF2w09jp 0umFh06RJqywFRRV0E0CvftiaR6KzC/1eVcCSTJaUeM+O2EeUljNtq9QIYXfYFlkhFK7u5d9TlG+ vhHiIkLKnK7vtpp8AHGcCQMLFlAFzAZhtGZw/PLkELXHajQjjPxkHIJdJez9zlxFrXi04fcwAfLH nthjnlTZwWU7URNVE8PR5Anx8fVAIohlLp9inHbHE5Be5h2cpVeDuxR2Bkp1dMcZjJK6F9tHphpm 3ZEsZReHcPCrckysMmvFrC4T3wHpOxms5KvM+RkjapkGuOvqr6HMIT66Qw0RI4Lmdu+nRywWLCKo Q=
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/-kJbd1Sqetycvn_VZPjoqr-hFKI>
Subject: Re: [openpgp] To bind or not to bind
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: Sat, 23 Mar 2024 11:28:30 -0000

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

> On Fri 2024-03-22 19:19:53 +0100, Justus Winter wrote:
>>>  (2) Whether PQC encryption algorithms can be used only with SEIPDv2
>>
>> No, don't bind PQC encryption to SEIPDv2.  It should be possible to have
>> a "PKESKv3(classical) PKESKv6(PQC) SEIPDv1" message:
>
> I don't think this packet sequence is correct.  In particular, the PKESK
> version is bound to the following SEIPD version, *not* to the key
> version.
>
> In this case, i believe the right outcome would be:
>
>    PKESKv3(classical) PKESKv3(PQC) SEIPDv1

Yes, you are right.

Best,
Justus

v2.23.0 | Report a Bug | By Email