IETF Logo Mail Archive

Re: [openpgp] To bind or not to bind

Aron Wussler <aron@wussler.it> Sat, 23 March 2024 22:38 UTC

Return-Path: <aron@wussler.it>
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 5A056C14F6A9 for <openpgp@ietfa.amsl.com>; Sat, 23 Mar 2024 15:38:11 -0700 (PDT)
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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=wussler.it
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 eW9t_QcEezEM for <openpgp@ietfa.amsl.com>; Sat, 23 Mar 2024 15:38:06 -0700 (PDT)
Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 620AFC14F6A5 for <openpgp@ietf.org>; Sat, 23 Mar 2024 15:38:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wussler.it; s=protonmail3; t=1711233484; x=1711492684; bh=WAfKH5qelSHhCI91pyAl4KNX3uREceqchQojRsm8brA=; 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; b=ov84Kr5AAJ1+rw137LqydVQegz2v/aHstk07JVwqbc/fQ2KRISd7VvECjO63vwryN Edfq5ITigbUE0yhmR+kspg77/7+0H8LY99PoNef3oj4+Az3PSIxAOJ2zYwwCPBeOlV d43/Khxtmebo0WjDMh4ZtNhR14pI7S5mkzfkt9wfsinELCF01IO3SastAJlniapWI2 3x/9Q6jQG+tE8aMFdgpq7rGVtortF+pZe8wDOLqJzrOiKbW4Y4DVsMlifKolFJ9U3y VfOOaFNksSGoCrovayiTHGcISG07+DRxmazUtjyvDo2QfJNXi+Fvh3dVKGsBTSiCIq 27Z4fE1gwGI3Q==
Date: Sat, 23 Mar 2024 22:37:34 +0000
To: Justus Winter <justus@sequoia-pgp.org>
From: Aron Wussler <aron@wussler.it>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
Message-ID: <mUg-9v4FTMUYeDGa3AimMKuJI7Zy5ycxfEpfHN64enr0BP85qK6-Pt3lcgD-VzUfNLBMy2DLha7k_cmP8YXu2c_yMj68sVsPecwOpsiRItA=@wussler.it>
In-Reply-To: <WKKpi2FW6r9Pftm6kgrVNtXvOXa2U9kz9R0wqlGYuPDl9nRkrcvVM3a2cfviolf1XN83lhPh2KxfzXb2A6d8HeQ4qdKYNd8LlqbtC1cRgCM=@wussler.it>
References: <EGivTgyfjNm_TAvhds1OPA2c0O6LP9lFnkwWHHKLJY8ReJOgtDh3tnYsCSR8yrrBLbpeehtUgIJEhynae8L3daRimNiGO7BAb3cVvC66q-4=@wussler.it> <87a5mqi0xi.fsf@europ.lan> <WKKpi2FW6r9Pftm6kgrVNtXvOXa2U9kz9R0wqlGYuPDl9nRkrcvVM3a2cfviolf1XN83lhPh2KxfzXb2A6d8HeQ4qdKYNd8LlqbtC1cRgCM=@wussler.it>
Feedback-ID: 10883271:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------558b71a1cec4ddb13972d871b51af7a2692d2685d68189de4f5303ed5af635a0"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/UAwWfC_4Cz49RiF7GBo1RzGt6nY>
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 22:38:11 -0000

I need to correct myself:

> I somehow still think that *allowing* V4 PQC encryption still pushes toward V6 (note that to get regulatory compliance and signatures you need V6),
> and I am not so sure those test failures matter that much.

And add an explanation, the test failures are:
- pgpy that is a fairly niche implementation
- gopenpgp that is mostly in control of a single provider (and we should take care of updating our clients to v3)
- rnp, that AFAIK mostly affects Thunderbird. Given that Kai seems to be fairly supportive of v4, it's in his interest adding that flag to the packaged build.

Aron

v2.23.0 | Report a Bug | By Email