vanitasvitae/openpgp-notes
1
0
Fork 0
mirror of https://codeberg.org/openpgp/notes.git synced 2024-11-30 03:22:06 +01:00
Code Issues Projects Releases Packages Wiki Activity

Note that DKS is preferred in v6

Browse source
This commit is contained in:
Heiko Schaefer 2023-11-21 12:30:18 +01:00
parent ade8edd697
commit ae2c732730
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/04-certificates.md
View file

@ -176,7 +176,7 @@ For example, the capabilities of a component key, such as *signing* or *encrypti
Instead, this kind of metadata is stored as part of the signature packets that join components into an OpenPGP certificate: Instead, this kind of metadata is stored as part of the signature packets that join components into an OpenPGP certificate:
- For the primary key, its key flags and other metadata can be defined in two ways: - For the primary key, its key flags and other metadata can be defined in two ways:
- With a [direct key signature](direct_key_signature) on the primary key, - With a [direct key signature](direct_key_signature) on the primary key (preferred method in OpenPGP version 6),
- or by associating the metadata with the [Primary User ID](primary_user_id). - or by associating the metadata with the [Primary User ID](primary_user_id).
- For subkeys, metadata is defined with the [subkey binding signature](binding_subkeys) that links the subkey to the certificate. - For subkeys, metadata is defined with the [subkey binding signature](binding_subkeys) that links the subkey to the certificate.
- For identity components like User IDs, metadata is associated via the [certifying self-signature](bind_ident) that links the identity to the certificate. - For identity components like User IDs, metadata is associated via the [certifying self-signature](bind_ident) that links the identity to the certificate.