mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-23 08:02:05 +01:00
minor restructure
This commit is contained in:
parent
03f8bf21c1
commit
6440318fcc
1 changed files with 16 additions and 16 deletions
|
@ -18,22 +18,6 @@ In this chapter, we'll discuss signatures that apply to component keys and ident
|
||||||
Types of signatures in OpenPGP
|
Types of signatures in OpenPGP
|
||||||
```
|
```
|
||||||
|
|
||||||
## Types of signatures on components
|
|
||||||
|
|
||||||
There are two classes of components that signatures can apply to:
|
|
||||||
|
|
||||||
- Component keys (primary keys or subkeys).
|
|
||||||
- Identity components (User IDs or User attributes).
|
|
||||||
|
|
||||||
And there are two important scenarios that we will distinguish. Signatures on components can be issued by:
|
|
||||||
|
|
||||||
- The certificate's owner (in which case we call them *self-signatures*), or
|
|
||||||
- A third party (in which case we call them *third-party signatures*).
|
|
||||||
|
|
||||||
The same OpenPGP signature mechanism is used for all of these cases. So at first, we will discuss the general shape of OpenPGP signatures.
|
|
||||||
|
|
||||||
However, there are differences in some of the details of the signatures for these different cases, which we will then look into - as well as the semantics, which differ between these types of signatures. We'll discuss all of this in this chapter.
|
|
||||||
|
|
||||||
## Signatures in OpenPGP
|
## Signatures in OpenPGP
|
||||||
|
|
||||||
The term *signature* can have multiple meanings in the context of the OpenPGP specification:
|
The term *signature* can have multiple meanings in the context of the OpenPGP specification:
|
||||||
|
@ -72,6 +56,22 @@ If Alice is certain that `Bob Baker <bob@example.com>` controls the key `0xB0B`,
|
||||||
Bob can then add this signature to his certificate.
|
Bob can then add this signature to his certificate.
|
||||||
TODO: More WoT.
|
TODO: More WoT.
|
||||||
|
|
||||||
|
##### Types of signatures on components
|
||||||
|
|
||||||
|
There are two classes of components that signatures can apply to:
|
||||||
|
|
||||||
|
- Component keys (primary keys or subkeys).
|
||||||
|
- Identity components (User IDs or User attributes).
|
||||||
|
|
||||||
|
And there are two important scenarios that we will distinguish. Signatures on components can be issued by:
|
||||||
|
|
||||||
|
- The certificate's owner (in which case we call them *self-signatures*), or
|
||||||
|
- A third party (in which case we call them *third-party signatures*).
|
||||||
|
|
||||||
|
The same OpenPGP signature mechanism is used for all of these cases. So at first, we will discuss the general shape of OpenPGP signatures.
|
||||||
|
|
||||||
|
However, there are differences in some of the details of the signatures for these different cases, which we will then look into - as well as the semantics, which differ between these types of signatures. We'll discuss all of this in this chapter.
|
||||||
|
|
||||||
##### Revocations
|
##### Revocations
|
||||||
|
|
||||||
One important class of self-signatures are revocations.
|
One important class of self-signatures are revocations.
|
||||||
|
|
Loading…
Reference in a new issue