From 6dc243de9820fc170018cfc2c6cb43609dd97c05 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Sat, 11 Nov 2023 18:45:18 +0100 Subject: [PATCH] ch7: Write "transformations" section about CSF --- book/source/07-signing_data.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/book/source/07-signing_data.md b/book/source/07-signing_data.md index cc0385c..ef18212 100644 --- a/book/source/07-signing_data.md +++ b/book/source/07-signing_data.md @@ -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. +(data_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 -```{admonition} TODO -:class: warning +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. -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 (``). #### Pitfalls