mirror of
https://codeberg.org/openpgp/notes.git
synced 2025-09-11 04:09:41 +02:00
Extract TODOs as tickets
Signed-off-by: David Runge <dave@sleepmap.de>
This commit is contained in:
parent
910b4f9976
commit
a17a3a30f2
14 changed files with 21 additions and 147 deletions
|
@ -49,13 +49,7 @@ In addition to these {term}`subpackets<OpenPGP Signature Subpacket>`, {term}`sel
|
|||
|
||||
### Remove or revoke a User ID
|
||||
|
||||
Since {term}`OpenPGP certificates<OpenPGP certificate>` are often distributed by the means of {term}`key servers<Key Server>`, new {term}`signatures<OpenPGP Signature Packet>` on a {term}`certificate<OpenPGP Certificate>` are often "merged" into existing copies of the {term}`certificate<OpenPGP Certificate>` locally by the recipient.
|
||||
|
||||
```{admonition} TODO
|
||||
:class: warning
|
||||
|
||||
Link to the "Merging" section in chapter 4, once merged.
|
||||
```
|
||||
Since {term}`OpenPGP certificates<OpenPGP certificate>` are often distributed by the means of {term}`key servers<Key Server>`, new {term}`signatures<OpenPGP Signature Packet>` on a {term}`certificate<OpenPGP Certificate>` are often "[merged](certificate-merging)" into existing copies of the {term}`certificate<OpenPGP Certificate>` locally by the recipient.
|
||||
|
||||
This integration process means it is practically impossible to directly remove {term}`signatures<OpenPGP Signature Packet>` or {term}`User IDs<User ID>` from a {term}`certificate<OpenPGP Certificate>`, as there is no way to communicate the intention of {term}`packet<OpenPGP Signature Packet>` deletion to the recipient.
|
||||
|
||||
|
@ -110,12 +104,6 @@ In {term}`Subkey Revocation signatures<Subkey Revocation Signature Packet>`, the
|
|||
|
||||
Note that a value of `32` is not applicable in these {term}`signatures<OpenPGP Signature Packet>`.
|
||||
|
||||
```{admonition} TODO
|
||||
:class: warning
|
||||
|
||||
Research and explain hardness in the context of subkey revocations. What does a hard subkey revocation express concretely?
|
||||
```
|
||||
|
||||
### Revoke a certificate
|
||||
|
||||
Users may find themselves needing to revoke their entire {term}`OpenPGP certificate`, rendering it unusable. This could be for various reasons, such as migrating to a new {term}`certificate<OpenPGP certificate>` or in response to a compromise of the {term}`certificate<OpenPGP certificate>`'s {term}`secret key material<Private Key Material>`.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue