mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-27 01:52:06 +01:00
edit ch4 subkeys
This commit is contained in:
parent
4bcb73e5ec
commit
5eb49aee3e
1 changed files with 5 additions and 5 deletions
|
@ -95,15 +95,15 @@ In the RFC, the OpenPGP primary key is occasionally referred to as "top-level ke
|
||||||
|
|
||||||
#### Subkeys
|
#### Subkeys
|
||||||
|
|
||||||
In addition to the primary key, modern OpenPGP certificates usually contain a number of "subkeys" (however, it's not technically necessary for a certificate to contain subkeys).
|
In addition to the primary key, modern OpenPGP certificates usually contain several subkeys, although they are not technically required.
|
||||||
|
|
||||||
Subkeys have the same structure as the primary key, but they are used in a different role. Subkeys are cryptographically linked with the primary key (more on this below).
|
Subkeys have the same structural attributes as the primary key but fulfill a different role. Subkeys are cryptographically linked with the primary key (elaborated below).
|
||||||
|
|
||||||
```{figure} diag/Subkeys.png
|
```{figure} diag/Subkeys.png
|
||||||
:name: Certificate with Subkeys
|
:name: Certificate with subkeys
|
||||||
:alt: Three component keys. The primary key is shown at the top. It can be used for certification. Below it, linked with arrows, are two more component keys, used as subkeys. They are marked as "for encryption" and "for signing", respectively.
|
:alt: Three component keys depicted. The primary key is positioned at the top, designated for certification. Below it, linked by arrows, are two more component keys, used as subkeys. They are labeled as "for encryption" and "for signing," respectively.
|
||||||
|
|
||||||
OpenPGP certificates can contain a number of subkeys
|
OpenPGP certificates can contain multiple subkeys.
|
||||||
```
|
```
|
||||||
|
|
||||||
#### Key Flags: defining which operations a component key can perform
|
#### Key Flags: defining which operations a component key can perform
|
||||||
|
|
Loading…
Reference in a new issue