From 32b5e0cfe0939c82d0d9087d742a82939d3d80d4 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Wed, 15 Nov 2023 19:11:59 +0100 Subject: [PATCH] Align wording with https://gitlab.com/openpgp-wg/rfc4880bis/-/merge_requests/354/diffs --- 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 53fe87f..4d373d5 100644 --- a/book/source/07-signing_data.md +++ b/book/source/07-signing_data.md @@ -133,7 +133,7 @@ The cleartext signature framework includes specific text normalization procedure _ **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 binary [text signatures](data_signature_types), the 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. +- **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. #### Pitfalls