Re: [openpgp] crypto-refresh finished? (again;-)

Paul Schaub <vanitasvitae@fsfe.org> Wed, 21 June 2023 17:43 UTC

Return-Path: <vanitasvitae@fsfe.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 74726C151991 for <openpgp@ietfa.amsl.com>; Wed, 21 Jun 2023 10:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.932
X-Spam-Level:
X-Spam-Status: No, score=-1.932 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 uUtsyF-4ewm0 for <openpgp@ietfa.amsl.com>; Wed, 21 Jun 2023 10:43:02 -0700 (PDT)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 8E352C14F736 for <openpgp@ietf.org>; Wed, 21 Jun 2023 10:43:02 -0700 (PDT)
Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (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 mx1.riseup.net (Postfix) with ESMTPS id 4QmW7B04TJzDqXG for <openpgp@ietf.org>; Wed, 21 Jun 2023 17:43:01 +0000 (UTC)
X-Riseup-User-ID: 82D5CBF6E355EDF8030AEF7DB4C6A1BB10B6999F3F109360C7A322ACC8C6BF69
Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4QmW7943S4zJnsg for <openpgp@ietf.org>; Wed, 21 Jun 2023 17:43:01 +0000 (UTC)
Message-ID: <fb1d310d-f70a-d1d7-abe4-bcedac6be932@fsfe.org>
Date: Wed, 21 Jun 2023 19:43:00 +0200
MIME-Version: 1.0
Content-Language: en-US
To: openpgp@ietf.org
References: <7b9d62a6-8570-ca81-c0bd-0f31d6cd136c@cs.tcd.ie>
From: Paul Schaub <vanitasvitae@fsfe.org>
In-Reply-To: <7b9d62a6-8570-ca81-c0bd-0f31d6cd136c@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/Gu_5P8l7KiIdKRhl9AnS9XMZUZg>
Subject: Re: [openpgp] crypto-refresh finished? (again;-)
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: Wed, 21 Jun 2023 17:43:03 -0000

As the maintainer of PGPainless I too support the publication of the 
crypto-refresh document.

I started to propose patches[1] for v6 features for Bouncy Castle a 
while ago, and a number of features are already supported by both BC and 
PGPainless (e.g. v6 SKESKs + v2 SEIPDs).

[1]: https://github.com/bcgit/bc-java/issues/1421