mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-23 08:02:05 +01:00
ch7: Write "transformations" section about CSF
This commit is contained in:
parent
1b5edc1774
commit
6dc243de98
1 changed files with 3 additions and 4 deletions
|
@ -17,6 +17,7 @@ Data signatures can only be issued by component keys with the *signing* [key fla
|
||||||
|
|
||||||
Note that signatures over data are distinct from {ref}`component_signatures_chapter`, which are used to attach metadata or subkeys to a certificate.
|
Note that signatures over data are distinct from {ref}`component_signatures_chapter`, which are used to attach metadata or subkeys to a certificate.
|
||||||
|
|
||||||
|
(data_signature_types)=
|
||||||
## Signature types
|
## Signature types
|
||||||
|
|
||||||
OpenPGP data signatures use one of two [signature types](signature_types):
|
OpenPGP data signatures use one of two [signature types](signature_types):
|
||||||
|
@ -125,11 +126,9 @@ This combination can be attractive for processes where signed messages are handl
|
||||||
|
|
||||||
#### Text transformations for cleartext signatures
|
#### Text transformations for cleartext signatures
|
||||||
|
|
||||||
```{admonition} TODO
|
In the cleartext signature framework, the message text is normalized by [escaping dashes](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-dash-escaped-text), to prevent parsing problems where message content and armor headers are confused.
|
||||||
:class: warning
|
|
||||||
|
|
||||||
explain text transformations for cleartext signatures (LF->CRLF and additional escaping)
|
Additionally, as usual for [text signatures](data_signature_types), the signature is calculated on the text with normalized line endings (`<CR><LF>`).
|
||||||
```
|
|
||||||
|
|
||||||
#### Pitfalls
|
#### Pitfalls
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue