[openpgp] [Errata Verified] RFC4880 (7889)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 21 April 2024 02:38 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 3DA4AC14F689; Sat, 20 Apr 2024 19:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level:
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_BLOCKED=0.001, 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=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 OUUF7Q0Za3T0; Sat, 20 Apr 2024 19:38:24 -0700 (PDT)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (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 28CC1C14F60D; Sat, 20 Apr 2024 19:38:24 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id DFF9D8526E; Sat, 20 Apr 2024 19:38:23 -0700 (PDT)
To: dkg@fifthhorseman.net, jon@callas.org, lutz@iks-jena.de, hal@finney.org, dshaw@jabberwocky.com, rodney@canola-jones.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: paul.wouters@aiven.io, iesg@ietf.org, openpgp@ietf.org, iana@iana.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20240421023823.DFF9D8526E@rfcpa.amsl.com>
Date: Sat, 20 Apr 2024 19:38:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/3S3Y4vk7Ppmql-dotn95bgU8jPE>
X-Mailman-Approved-At: Sun, 21 Apr 2024 08:17:11 -0700
Subject: [openpgp] [Errata Verified] RFC4880 (7889)
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, 21 Apr 2024 02:38:28 -0000
The following errata report has been verified for RFC4880, "OpenPGP Message Format". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7889 -------------------------------------- Status: Verified Type: Technical Reported by: Daniel Kahn Gillmor <dkg@fifthhorseman.net> Date Reported: 2024-04-10 Verified by: Paul Wouters (IESG) Section: 5.2.3.23 Original Text ------------- Note that any signature may be revoked, including a certification on some other person's key. Corrected Text -------------- Note that any certification may be revoked, including a certification on some other person's key. Notes ----- the only three types of revocation that are specified in OpenPGP are: 0x20: Key revocation signature The signature is calculated directly on the key being revoked. A revoked key is not to be used. Only revocation signatures by the key being revoked, or by an authorized revocation key, should be considered valid revocation signatures. 0x28: Subkey revocation signature The signature is calculated directly on the subkey being revoked. A revoked subkey is not to be used. Only revocation signatures by the top-level signature key that is bound to this subkey, or by an authorized revocation key, should be considered valid revocation signatures. 0x30: Certification revocation signature This signature revokes an earlier User ID certification signature (signature class 0x10 through 0x13) or direct-key signature (0x1F). It should be issued by the same key that issued the revoked signature or an authorized revocation key. The signature is computed over the same data as the certificate that it revokes, and should have a later creation date than that certificate. There is no explicit mechanism to revoke a document signature (as opposed to a certification signature), so it makes no sense to claim that "any signature may be revoked". This was observed by Andrew Gallagher in https://gitlab.com/dkg/openpgp-revocation/-/issues/15, and is still an issue in the successor to RFC 4880, draft-ietf-openpgp-crypto-refresh ☹ -------------------------------------- RFC4880 (draft-ietf-openpgp-rfc2440bis-22) -------------------------------------- Title : OpenPGP Message Format Publication Date : November 2007 Author(s) : J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer Category : PROPOSED STANDARD Source : Open Specification for Pretty Good Privacy Stream : IETF Verifying Party : IESG
- [openpgp] [Errata Verified] RFC4880 (7889) RFC Errata System