[openpgp] Key Superseded signature type

Aron Wussler <aron@wussler.it> Fri, 02 December 2022 21:36 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 6C998C14CE26 for <openpgp@ietfa.amsl.com>; Fri, 2 Dec 2022 13:36:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_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=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 9p-QHHsJwX45 for <openpgp@ietfa.amsl.com>; Fri, 2 Dec 2022 13:36:13 -0800 (PST)
Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) (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 DC5E4C14CE2B for <openpgp@ietf.org>; Fri, 2 Dec 2022 13:36:12 -0800 (PST)
Date: Fri, 02 Dec 2022 21:36:01 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wussler.it; s=protonmail3; t=1670016968; x=1670276168; bh=fbD4LXXWdETt8qy5CSuAJsKns9jcjR/bsfMxBaLfu54=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=vqH5wOLdUlX7dPYiXO1qTLsq81RRc+h2RW0tKdQH651ooIqNCDt5yIdrIXX7512Zv 107ZI6uWem02x5J5mdpRDoeMeSTX+Xn1XBEPwDo/HJOZ6TNQrSTPPAw9YLqdKDa7Vt Rnfccata0vv3Ln0vMHdWfHgIytr1jF8BSUHY84IAhf+/8gX6ClBAEaLWWjd1vUOFXb EgtFOzEv1btmgWW9zT0WyAimo+Sqo1K9t3dFgSoH5QA1ARbJxJajpDkloAvI0ZSfDD K8ZyVYzgiJO7Vx6rDlJfV/BBZ9NGbYOB4hKwmgDZnXAge1SZhjloGFRsXL1cjsqqgt QLiv+pD8EJwbw==
To: "openpgp@ietf.org" <openpgp@ietf.org>
From: Aron Wussler <aron@wussler.it>
Message-ID: <l9nQMx7kDFEUhLWo6aN4ttO1E5Jp-TsKdnTMrbfNn6IgW4mHOXdT2EonIdEJ4neAkRffB9Tmf-eWZTocci2mUqhl3-zqd5xTS2nAlXg6nUM=@wussler.it>
Feedback-ID: 10883271:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------d457019564d67141379be45d4a02e1a056af7b7b8848c316f747be9db4644b6e"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/jXFhPq6OpiPDMZETVdaBeiNQNsc>
Subject: [openpgp] Key Superseded signature type
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: Fri, 02 Dec 2022 21:36:18 -0000

Hi everyone,

I've got another small proposal for the crypto-refresh, also coming from the OpenPGP summit.

We've been discussing about the options for the v4 -> v5 transition (I guess v6 now?), and I'm a big fan of having multiple independently generated certificates, and allowing a smooth transition between them.

In OpenPGP we don't have a mechanism to signal a superseded or deprecated key, and I fear that if we all wait for v6 keys to be understood from the majority of software and then atomically switch to v6 revoking our old v4 keys we'll wait for a long time. The alternative is to have two cross-signed certificates, and publishing them both, hoping for people to use the newer one.

With this proposal, my objective is to have a standardized way to tackle this, by introducing a new signature type that signals key deprecation with a pointer to the new key.
This would automatically extend to future transitions (e.g. PQC), and allow for an easier key rotation (It would be allowed on hard revocation too).

https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/222

All kind of feedback is welcome, whether this means
(1) not introducing this feature at all
(2) introducing this feature but later
(3) introducing this feature now

Cheers,
Aron

--
Aron Wussler
Sent with ProtonMail, OpenPGP key 0x7E6761563EFE3930