mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-29 11:02:06 +01:00
edits to commit f6bec55df5
This commit is contained in:
parent
100e29278c
commit
463030f945
1 changed files with 3 additions and 3 deletions
|
@ -251,13 +251,13 @@ Additionally, OpenPGP allows modeling User ID-specific preferences. The idea is
|
|||
|
||||
## A typical OpenPGP certificate, revisited
|
||||
|
||||
Now that we've discussed how keys and identity components are linked together, we can have another look at the certificate from {numref}`fig-openpgp-certificate-components`. This time we include all of its binding signatures, as well as a direct key signature that contains metadata for the full certificate:
|
||||
Following our review of how keys and identity components are linked, let's reexamine the OpenPGP certificate from {numref}`fig-openpgp-certificate-components`. Our focus not extends to all of its binding signatures and the direct key signature that contains metadata for the full certificate:
|
||||
|
||||
```{figure} diag/OpenPGP_Certificate.png
|
||||
:name: fig-openpgp-certificate
|
||||
:alt: Depicts an OpenPGP certificate, including a set of components, binding signatures and a direct key signature on the primary key.
|
||||
:alt: Depicts an OpenPGP certificate, including a set of components, binding signatures, and a direct key signature on the primary key.
|
||||
|
||||
A typical OpenPGP certificate, including binding signatures for all of its components, and a signature that associates metadata with the primary key
|
||||
This shows a typical OpenPGP certificate, including binding signatures for all of its components, and a signature that associates metadata with the primary key.
|
||||
```
|
||||
|
||||
## Revocations
|
||||
|
|
Loading…
Reference in a new issue