Re: [openpgp] Multi-algo pubkey, or how to create future-proof keys

Werner Koch <> Mon, 21 June 2021 09:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C0E863A2A7D for <>; Mon, 21 Jun 2021 02:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id f8H-zcX8ww7Q for <>; Mon, 21 Jun 2021 02:50:13 -0700 (PDT)
Received: from ( [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BCAF73A2A74 for <>; Mon, 21 Jun 2021 02:50:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=20181017; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=H6eeF42m07kfOh9yOy7duhvTCx6e2WSA+sVWIgWyYek=; b=CHDGOWHNDmeIelks4l1yCXUgBL DVGHAntoYdp1qeDbnWxYsag+fdL2o5wWe+uI3bXy+h+VYhMDT1qUMllxqIZfPeozTKwAh59zxDCRR BeCnvTw40prx47IXmC3jU+WYQYEr2JRCMJz0baj7DS/6k/1uVWnHtz/AgrsyLTIcWexY=;
Received: from uucp by with local-rmail (Exim 4.89 #1 (Debian)) id 1lvGZF-0007zO-2e for <>; Mon, 21 Jun 2021 11:50:09 +0200
Received: from wk by with local (Exim 4.92 #5 (Debian)) id 1lvGXO-0006Sj-Ae; Mon, 21 Jun 2021 11:48:14 +0200
From: Werner Koch <>
To: =?utf-8?Q?=C3=81ngel?= <>
References: <>
Organisation: GnuPG e.V.
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Mail-Followup-To: =?utf-8?Q?=C3=81ngel?= <>,
Date: Mon, 21 Jun 2021 11:48:14 +0200
In-Reply-To: <> (=?utf-8?Q?=22=C3=81ngel=22's?= message of "Mon, 21 Jun 2021 03:16:42 +0200")
Message-ID: <>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=investigation_BECCA_SIG_FIS_Power_outage_Maritime_domain_awarenes_NC"; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <>
Subject: Re: [openpgp] Multi-algo pubkey, or how to create future-proof keys
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 21 Jun 2021 09:50:19 -0000

On Mon, 21 Jun 2021 03:16, Ángel said:

> Regarding scope, it seems suitable to include into the cryptography
> revision and, although not strictly required, being included with a
> major version would probably be helpful.

This is not part of the WG charter and thus this should be deferred for
a future revision.  It is also possible, as you noted, that this can be
done as a new algo. Fortunately 4480bis has a goal to make it easier to
come up with new algorithms.

n any case, it is always possible to write an I-D for an extension of
OpenPGP. We did this for ECC and I think this is the best way for new
experimental algorithms.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.