ch7: Write "transformations" section about CSF

This commit is contained in:
Heiko Schaefer 2023-11-11 18:45:18 +01:00
parent 1b5edc1774
commit 6dc243de98
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB

View file

@ -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