mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-26 17:42:06 +01:00
move todo into advanced section branch, add link
This commit is contained in:
parent
f35044bd68
commit
d157a4d1fc
1 changed files with 1 additions and 8 deletions
|
@ -148,14 +148,7 @@ Within a certificate, a specific User ID is designated as the [Primary User ID](
|
||||||
|
|
||||||
Each User ID carries associated preference settings, such as preferred encryption algorithms, which is detailed in {numref}`zooming_in_user_id`). The preferences associated with the Primary User ID take precedence by default.
|
Each User ID carries associated preference settings, such as preferred encryption algorithms, which is detailed in {numref}`zooming_in_user_id`). The preferences associated with the Primary User ID take precedence by default.
|
||||||
|
|
||||||
```{admonition} TODO
|
The primary User ID was historically sometimes used to store preferences that apply to the certificate as a whole. For more details on this, see {ref}`dks-puid`.
|
||||||
:class: warning
|
|
||||||
|
|
||||||
i think crypto-refresh suggests that the direct key signature should hold the default preferences?
|
|
||||||
we might need to write a more nuanced text here, about how DKS and primary user id interact in v6, and mention the differences to v4?
|
|
||||||
|
|
||||||
the primary User ID can also specify metadata about the primary key
|
|
||||||
```
|
|
||||||
|
|
||||||
### User attributes in OpenPGP
|
### User attributes in OpenPGP
|
||||||
While
|
While
|
||||||
|
|
Loading…
Reference in a new issue