From 16d444207395244096a8eed435d310d2cf7b97fd Mon Sep 17 00:00:00 2001 From: "Tammi L. Coles" Date: Mon, 4 Dec 2023 11:19:41 +0000 Subject: [PATCH] ed ch8 feedback commit e59e70939c --- book/source/08-signing_components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/08-signing_components.md b/book/source/08-signing_components.md index 9cdb2a4..8015b72 100644 --- a/book/source/08-signing_components.md +++ b/book/source/08-signing_components.md @@ -52,7 +52,7 @@ Third-party signatures are used to make specific statements: The **certify others** [key flag](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-key-flags) (`0x01`) is required to issue third-party signatures. By convention[^primary-certification], only the certificate's primary key can hold this key flag. ``` -[^primary-certification]: Most implementations currently assume that only the primary key may hold the "certify others" key flag. However, the RFC doesn't clearly specify this limitation. +[^primary-certification]: Most current implementations assume that only the primary key may hold the *certify others* key flag, although this is not specified in the RFC. ### Distinct functions of self-signatures and third-party signatures