From 708b7cc64c996c18cc78ec2d7ea8e5a10a0f7629 Mon Sep 17 00:00:00 2001 From: "Tammi L. Coles" Date: Fri, 19 Jan 2024 16:23:25 +0100 Subject: [PATCH] edit ch20 on signature packet versions --- book/source/adv/signatures.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/book/source/adv/signatures.md b/book/source/adv/signatures.md index 6de0960..2c0b80c 100644 --- a/book/source/adv/signatures.md +++ b/book/source/adv/signatures.md @@ -39,15 +39,13 @@ In contrast, when a message is created for a specific recipient, the sender can In this workflow, the signed hash digest is created with a hash algorithm that meets the recipient's preferences as well as the sender's capabilities and preferences. -## Signature versions +## Conforming to signature packet versions -As described in the [RFC](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-signature-packet-type-id-2), the version of a generated signature packet must conform to the version of the key that issues the signature. - -That is: +As described in the [RFC](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-signature-packet-type-id-2), the version of a generated signature packet must conform to the version of the key used to issue it. Specifically: - OpenPGP version 6 keys must generate version 6 signature packets - OpenPGP version 4 keys must generate version 4 signature packets -Note that some historical version 3 signature packets may still be relevant for applications that handle old OpenPGP data[^sig-v3]. These version 3 signature packets will have been generated by version 4 keys. +Some version 3 signature packets, while historical, may still be relevant for applications that handle legacy OpenPGP data[^sig-v3]. These version 3 signature packets will have been generated by version 4 keys. -[sig-v3]Version 4 signature packets were introduced in [RFC 2440](https://datatracker.ietf.org/doc/html/rfc2440#section-5.2) in 1998, which specifies that applications SHOULD generate v4 signature, however generation of v3 signature packets has remained allowed through [RFC 4880](https://www.rfc-editor.org/rfc/rfc4880.html#section-5.2). +[sig-v3]Version 4 signature packets were introduced in [RFC 2440](https://datatracker.ietf.org/doc/html/rfc2440#section-5.2) in 1998, which specifies that applications *should* generate v4 signatures. However, generation of v3 signature packets continued to be permissable as per [RFC 4880](https://www.rfc-editor.org/rfc/rfc4880.html#section-5.2). \ No newline at end of file