From 9b925ffd9c3b5566efa9d32a49e5b5589144648b Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Fri, 17 Nov 2023 00:14:09 +0100 Subject: [PATCH] fix list dash --- book/source/07-signing_data.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/07-signing_data.md b/book/source/07-signing_data.md index 5163be4..0b9952c 100644 --- a/book/source/07-signing_data.md +++ b/book/source/07-signing_data.md @@ -131,7 +131,7 @@ These features are particularly beneficial in scenarios where signed messages ar The cleartext signature framework includes specific text normalization procedures to ensure the integrity and clarity of the message: -_ **Escaping dashes**: The framework implements a method of [dash-escaped text](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-dash-escaped-text) within the message. Dash-escaping ensures that the parser correctly distinguishes between the armor headers, which are part of the signature's structure, and any lines in the message that happen to start with a dash. +- **Escaping dashes**: The framework implements a method of [dash-escaped text](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-dash-escaped-text) within the message. Dash-escaping ensures that the parser correctly distinguishes between the armor headers, which are part of the signature's structure, and any lines in the message that happen to start with a dash. - **Normalization of line endings**: Consistent with the approach for any other [text signature](data_signature_types), a cleartext signature is calculated on the text with normalized line endings (``). This ensures that the signature remains valid regardless of the text format of the receiving implementation.