Re: [openpgp] To bind or not to bind

Kai Engert <KaiE@kuix.de> Sun, 24 March 2024 07:31 UTC

Return-Path: <KaiE@kuix.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 51BE7C14F5F5 for <openpgp@ietfa.amsl.com>; Sun, 24 Mar 2024 00:31:02 -0700 (PDT)
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 (2048-bit key) header.d=kuix.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 1yhJe6m9voUu for <openpgp@ietfa.amsl.com>; Sun, 24 Mar 2024 00:30:58 -0700 (PDT)
Received: from cloud.kuix.de (cloud.kuix.de [93.90.207.85]) (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 3690BC14F5E8 for <openpgp@ietf.org>; Sun, 24 Mar 2024 00:30:57 -0700 (PDT)
Received: from [IPV6:2003:c8:af2a:a300:2b6a:161a:5cd:1ba] (p200300c8af2aa3002b6a161a05cd01ba.dip0.t-ipconnect.de [IPv6:2003:c8:af2a:a300:2b6a:161a:5cd:1ba]) by cloud.kuix.de (Postfix) with ESMTPSA id 6EAF219324E; Sun, 24 Mar 2024 07:30:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kuix.de; s=2018; t=1711265455; bh=0VCpkXXP4DgLMTvL5zG9glpSlEioBxLVS5KLbn4Q7Hc=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=NHR+qehdy6/tMHiqji0kG9yapaFqr8aE+riLlvTgjnQbdhKYGi29SFp4A78ck08Hh 62UiXBEHWzvC/rczPFzEtbG0hhitFk6kMtb8MiikxVvb9T8M8/IHp83CsuRcKwlAoK ARLZ0t/H1k4Zpt0BjflvAkU9/EoIVBqqcjpP5o7CHB4bj+4GbOS3BwXRVeSvwtL166 v7EhXoBjirdpLrbc+2vhEZPQeM1fE0mdcIk8kBwwu9I4oQhaRtzHgLB1yY64TpleTo sfMtZAR6CrKGqi7qcAMvzNkSeCRUIWCuqSKSn2ivNOvc2vqYYaUs/PFIw2pLl1oiEB 4mownj+S2H6zg==
Message-ID: <82300a06-fd34-47f5-a3db-26b99d87794e@kuix.de>
Date: Sun, 24 Mar 2024 08:30:55 +0100
MIME-Version: 1.0
User-Agent: Thunderbird Daily
Content-Language: en-US
To: Justus Winter <justus@sequoia-pgp.org>, Aron Wussler <aron@wussler.it>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
References: <EGivTgyfjNm_TAvhds1OPA2c0O6LP9lFnkwWHHKLJY8ReJOgtDh3tnYsCSR8yrrBLbpeehtUgIJEhynae8L3daRimNiGO7BAb3cVvC66q-4=@wussler.it> <87a5mqi0xi.fsf@europ.lan> <WKKpi2FW6r9Pftm6kgrVNtXvOXa2U9kz9R0wqlGYuPDl9nRkrcvVM3a2cfviolf1XN83lhPh2KxfzXb2A6d8HeQ4qdKYNd8LlqbtC1cRgCM=@wussler.it> <mUg-9v4FTMUYeDGa3AimMKuJI7Zy5ycxfEpfHN64enr0BP85qK6-Pt3lcgD-VzUfNLBMy2DLha7k_cmP8YXu2c_yMj68sVsPecwOpsiRItA=@wussler.it> <874jcwikie.fsf@europ.lan>
From: Kai Engert <KaiE@kuix.de>
In-Reply-To: <874jcwikie.fsf@europ.lan>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/4x818W828GAAiTWRs54FF1Ghg54>
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: Sun, 24 Mar 2024 07:31:02 -0000

On 24.03.24 00:41, Justus Winter wrote:
>> - 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.
> 
> And then we tell every downstream consumer of RNP that they must use
> this one weird trick when importing certificates or RNP will choke on
> PQC-enabled v4 keys?  That doesn't seem viable to me.

Well, my hope is that RNP will fix the bug and would support v4-pqc keys.

The trick is currently necessary for tolerance, because it doesn't 
support it yet.

Kai