clarify language

This commit is contained in:
Heiko Schaefer 2023-11-25 17:43:22 +01:00
parent 993da3ccf4
commit 77a0a69d78
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB

View file

@ -385,7 +385,7 @@ Note that a value of `32` is not applicable in these signatures.
Users may find themselves needing to revoke their entire OpenPGP certificate, rendering it unusable. This could be for various reasons, such as migrating to a new certificate or in response to a compromise of the certificate's secret key material. Users may find themselves needing to revoke their entire OpenPGP certificate, rendering it unusable. This could be for various reasons, such as migrating to a new certificate or in response to a compromise of the certificate's secret key material.
While a soft-revoked certificate can be re-validated at a later time with a new certification, a hard revocation is typically permanent. While a soft-revoked certificate can be re-validated at a later time with a new certification, a hard revocation is permanent.
The recommended way to revoke a certificate is by issuing a *KeyRevocation* signature (type `0x20`). Its structure is similar to that of a *CertificationRevocation* signature. The recommended way to revoke a certificate is by issuing a *KeyRevocation* signature (type `0x20`). Its structure is similar to that of a *CertificationRevocation* signature.