Re: [openpgp] To bind or not to bind

Heiko Schäfer <heiko.schaefer@posteo.de> Tue, 02 April 2024 10:11 UTC

Return-Path: <heiko.schaefer@posteo.de>
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 D19CAC14F61C for <openpgp@ietfa.amsl.com>; Tue, 2 Apr 2024 03:11:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.093
X-Spam-Level:
X-Spam-Status: No, score=-7.093 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=posteo.de
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 4J61DmxQnAnR for <openpgp@ietfa.amsl.com>; Tue, 2 Apr 2024 03:11:03 -0700 (PDT)
Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (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 CBA34C14F61A for <openpgp@ietf.org>; Tue, 2 Apr 2024 03:11:01 -0700 (PDT)
Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id DA85F240103 for <openpgp@ietf.org>; Tue, 2 Apr 2024 12:10:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1712052659; bh=tIgsi+sZf599JI70P1sh0u+Cilfw4VfhYVyd+NsFYqc=; h=Content-Type:Message-ID:Date:MIME-Version:Subject:To:From:From; b=gzWgZ+37URrwb+KiRtRvobO6SPrnwtweTU2ZRSeCD692itkYh2VHEF8lRsmZe9VOj 5louxAxrdul/gzPti/hyHKNnSNIPBW4NmccBooPRLs/0RW22sjd02gV41fsPX/eO11 4cIKmSD52rxlyRQFV+rm7TFRr9SxA2AeQqLiP3QKBt+jWKbVYV7wTRkOhmwHdG4xQe 57vmJZ0v1hV2aT9q+nhdI3faL9WBsXNnSCwprYVCCqkZMbzw7r4wNyimlr1lQarfrj 9BYtDFcz3J+wrlT1NyzNaMGGkQ6zeYBmK2PxSzn+QPhg/wKK9w8m5wvWqB4hX8hYWX 841AjmXZB0WlA==
Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4V83Yb3BrKz9rxL for <openpgp@ietf.org>; Tue, 2 Apr 2024 12:10:59 +0200 (CEST)
Received: from services.foundation.hs (services.foundation.hs [192.168.21.4]) by mail.foundation.hs (Postfix) with ESMTP id 164904EA82 for <openpgp@ietf.org>; Tue, 2 Apr 2024 12:10:59 +0200 (CEST)
Content-Type: multipart/alternative; boundary="------------KxxVP54rJ0q8wmaAfi0ymq0v"
Message-ID: <e87dd6cd-9dda-40b9-b4b8-c1c6d0eef949@posteo.de>
Date: Tue, 02 Apr 2024 10:10:58 +0000
MIME-Version: 1.0
To: openpgp@ietf.org
References: <87a5mqi0xi.fsf@europ.lan> <23B46D65-EAF7-43D0-A5F1-04D28B698559@andrewg.com> <87sf0h32d3.fsf@fifthhorseman.net> <cd9a18d9-2d13-48d2-98e0-2ae268f68215@mtg.de> <87y1a6has4.fsf@europ.lan> <14a80b96-9860-461d-b9fe-e38e3bf651b1@mtg.de> <87v858gcmv.fsf@europ.lan> <8169558D-E770-495C-89BB-93F9BD42035A@andrewg.com> <87sf0bhnjc.fsf@europ.lan> <tjnjaB52IRv2u1L5YENIvZ1NU0_AcMm3hH_sKvcDCg0Y9gD0cCE16H0A2Nqd0B6FnJ5rc_d_3ziyiNvDj1C0xlGWbHhkbqzjgwQD3abYUL8=@wussler.it>
Content-Language: en-US
From: Heiko Schäfer <heiko.schaefer@posteo.de>
In-Reply-To: <tjnjaB52IRv2u1L5YENIvZ1NU0_AcMm3hH_sKvcDCg0Y9gD0cCE16H0A2Nqd0B6FnJ5rc_d_3ziyiNvDj1C0xlGWbHhkbqzjgwQD3abYUL8=@wussler.it>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/wZp6ltm-90KW872Q38rkUOvyTiM>
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: Tue, 02 Apr 2024 10:11:08 -0000

Hello List,

On 4/2/24 09:56, Aron Wussler wrote:
> I can't see the irreparable damage that you're referring to. Making a
> key that a few implementations can't parse IMO offers the same friction
> than having an expired old key around, and having to distribute a new
> one to the contacts still using the old one.
>
> On the other hand, I think the argument "whatever is compatible with PQC
>   should also be compatible with V6" is a valid one - and this may boil
> down to Kai's point, that they're not ready to move to V6.
>
> I agree that adding a V4 PQC key is a bit of a dirty hack, but mandating
>   their refusal may be a too hard solution.

I agree with Aaron.

I have also not been convinced by the arguments against allowing the 
combination of PQC encryption with v4 keys.
As I see it, only allowing PQC encryption in combination with v6 keys is 
not the best trade-off.

Sure, there are risks and downsides to specifying PQC encryption subkeys 
on v4 keys/certificates.
But there are also risks and downsides to the alternative approach of 
specifying PQC encryption exclusively for v6 keys.

Heiko