mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-27 01:52:06 +01:00
moved "VISUAL" admonitions to #95
we should consider if we want such diagrams after the core writing phase (if we have time).
This commit is contained in:
parent
d44226d288
commit
b257e9a366
1 changed files with 0 additions and 12 deletions
|
@ -6,12 +6,6 @@ SPDX-License-Identifier: CC-BY-SA-4.0
|
|||
(cyrptography_chapter)=
|
||||
# Cryptographic concepts and terms
|
||||
|
||||
```{admonition} VISUAL
|
||||
:class: warning
|
||||
|
||||
- Show example visualizations for operations? (encrypt/decrypt and signing/verification - only if we're going to reuse the visual primitives later)
|
||||
```
|
||||
|
||||
## Cryptographic hash functions
|
||||
|
||||
[Cryptographic hash functions](https://en.wikipedia.org/wiki/Cryptographic_hash_function) take data strings of any length (like a text message or file) and output a fixed-size code, often called a "hash" or "digest." This hash acts like a unique identifier for the original data.
|
||||
|
@ -133,12 +127,6 @@ While "secret key" (as used in the OpenPGP RFC) and "private key" serve the same
|
|||
|
||||
In OpenPGP, digital signatures have diverse applications, extending beyond mere validation of a message's origin. They can signify various intents, including certification, consent, acknowledgment, or even revocation by the signer. The multifaceted nature of "statements" conveyed through digital signatures in cryptographic protocols is wide-ranging but crucial, allowing third parties to inspect/evaluate these statements for authenticity and intended purpose.
|
||||
|
||||
```{admonition} VISUAL
|
||||
:class: warning
|
||||
|
||||
- add visualization showing: message + private key (signing) = signature -> message + signature + public key (verification) = validation confirmed?
|
||||
```
|
||||
|
||||
Digital signatures in OpenPGP are used in two primary contexts:
|
||||
|
||||
- [Certification statements](certifications_chapter)
|
||||
|
|
Loading…
Reference in a new issue