vanitasvitae/openpgp-notes
1
0
Fork 0
mirror of https://codeberg.org/openpgp/notes.git synced 2024-11-23 08:02:05 +01:00
Code Issues Projects Releases Packages Wiki Activity

don't use the generic word "critical" in a context where it has a technical meaning

Browse source
This commit is contained in:
Heiko Schaefer 2023-11-25 17:39:47 +01:00
parent 887c5bf0e6
commit 993da3ccf4
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
book/source/08-signing_components.md
View file

@ -377,7 +377,7 @@ The structure of such a signature is straightforward:
| Reason for Revocation | Hashed | True | False | Determines soft or hard revocation | | Reason for Revocation | Hashed | True | False | Determines soft or hard revocation |
In `SubkeyRevocation` signatures, the [reason for revocation](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-reason-for-revocation) subpacket is critical. The values `1` (key superseded) and `3` (key retired and no longer used) indicate soft revocations, whereas values `0` (no reason) and `2` (key compromised) indicate hard revocations. In `SubkeyRevocation` signatures, the [reason for revocation](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-reason-for-revocation) subpacket can only have values in the range of `0-3`. The values `1` (key superseded) and `3` (key retired and no longer used) indicate soft revocations, whereas values `0` (no reason) and `2` (key compromised) indicate hard revocations.
Note that a value of `32` is not applicable in these signatures. Note that a value of `32` is not applicable in these signatures.