Re: [openpgp] Key Superseded signature type

Aron Wussler <aron@wussler.it> Sun, 04 December 2022 22:06 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 55A22C14F728 for <openpgp@ietfa.amsl.com>; Sun, 4 Dec 2022 14:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_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 aZSJ4tKq2vaH for <openpgp@ietfa.amsl.com>; Sun, 4 Dec 2022 14:06:44 -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 D5C8BC14F5E0 for <openpgp@ietf.org>; Sun, 4 Dec 2022 14:06:43 -0800 (PST)
Date: Sun, 04 Dec 2022 22:06:33 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wussler.it; s=protonmail3; t=1670191600; x=1670450800; bh=DLqRv5cuRrHtZVJpSHPEa59olU+aQe6FpzFHMGeLH8c=; 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=psVl78a842+GnpC39E0toIVG+0awBloBKlzL4/QU0biy2Mwk/hbZVgPrbqjOg87r3 XUD/z4etdIawQse5DPdKx95zrPMsTRnckxt4NdPOL7FUnixjph0RTVovcy+xbIG1+6 wcbPE/CQSYznJQN6+oQPtIT7Jc7YKWb/0/w2qfHLIbO8NWrGTwXMWH+LFjjHJvrLNp 7nakNfJWsLoP0Yi+KK7j8ARXfBZIdVfcvLqT0LUCiRmqK+xPO8DKmQhzBbjWG0oiXj G1xTOAgS+AkLa5ReV8f+X75e4XFF3njeh5sEeZVb/i4i5XYEx0M/3O98PXiqSNR0eB zp/e/H67MojRg==
To: "Neal H. Walfield" <neal@walfield.org>
From: Aron Wussler <aron@wussler.it>
Cc: "openpgp@ietf.org" <openpgp@ietf.org>
Message-ID: <7VMCm0erUzxytzbbUpSqgK-Dk_PpsaOm0rA192EcogHTgQjZE6L5_6ySWm1opeAOopqRpn436uVSnTr2xhLxdumA5RSgW4xgMzRsvCMZuJU=@wussler.it>
In-Reply-To: <874jub4awl.wl-neal@walfield.org>
References: <l9nQMx7kDFEUhLWo6aN4ttO1E5Jp-TsKdnTMrbfNn6IgW4mHOXdT2EonIdEJ4neAkRffB9Tmf-eWZTocci2mUqhl3-zqd5xTS2nAlXg6nUM=@wussler.it> <875yes4jcr.wl-neal@walfield.org> <khUP1FyJH596TsLOtPZTlXoqusoK_6mIkZvbSunQBgy-5RMLUdhlF_HVa4X4xi7TSA2qNe32izy4daFC72oFXFo0bVvKV2FF9oMWKL808sM=@wussler.it> <874jub4awl.wl-neal@walfield.org>
Feedback-ID: 10883271:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------7a754d2ad78b22ce995a69c26fabf2303d2f300127f5ba60f296a671330bd0ac"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/aa_k4yB7SvtmLhG2Y4H8Pm02J5A>
Subject: Re: [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: Sun, 04 Dec 2022 22:06:49 -0000

Hi Neal,

I've added a commit reflecting the various suggestions.

Cheers,
Aron



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



------- Original Message -------
On Sunday, December 4th, 2022 at 13:21, Neal H. Walfield <neal@walfield.org> wrote:


> On Sat, 03 Dec 2022 17:00:13 +0100,
> Aron Wussler wrote:
> 

> > > As I commented in the MR, I wonder if a new Reason for Revocation
> > > type, `Key is superseded by`, which takes a fingerprint and a human
> > > readable string, would be better than a new signature type.
> > 

> > I think this approach does not play well with legacy implementations, as they would consider the key revoked.
> 

> 

> That's a good point. Then perhaps 'Key is superseded' plus a
> subpacket or notation to indicate the new key would be better. Note
> 'Key is superseded' is a type of soft revocation:
> 

> If a key has been revoked because of a compromise, all signatures
> created by that key are suspect. However, if it was merely
> superseded or retired, old signatures are still valid.
> 

> Neal