mirror of
https://codeberg.org/openpgp/notes.git
synced 2025-12-09 15:11:08 +01:00
Merge branch 'draft' into tammi-ch4
# Conflicts: # book/source/04-certificates.md
This commit is contained in:
commit
8704758dde
71 changed files with 9144 additions and 804 deletions
|
|
@ -1,3 +1,8 @@
|
|||
<!--
|
||||
SPDX-FileCopyrightText: 2023 The "Notes on OpenPGP" project
|
||||
SPDX-License-Identifier: CC-BY-SA-4.0
|
||||
-->
|
||||
|
||||
(certificates_chapter)=
|
||||
# Certificates
|
||||
|
||||
|
|
@ -183,7 +188,7 @@ Currently, the OpenPGP standard prescribes only one format to be stored in user
|
|||
|
||||
## Linking the components
|
||||
|
||||
To form an OpenPGP certificate, individual components are interconnected by the certificate holder using their OpenPGP software. Within OpenPGP, this process is termed "binding," as in "a subkey is bound to the primary key." These bindings are realized using cryptographic signatures. An in-depth discussion of this topic can be found in {ref}`certifications_chapter`).
|
||||
To form an OpenPGP certificate, individual components are interconnected by the certificate holder using their OpenPGP software. Within OpenPGP, this process is termed "binding," as in "a subkey is bound to the primary key." These bindings are realized using cryptographic signatures. An in-depth discussion of this topic can be found in {ref}`component_signatures_chapter`).
|
||||
|
||||
In very abstract terms, the primary key of a certificate acts as a root of trust or "certification authority." It is responsible for:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue