mirror of
https://codeberg.org/openpgp/notes.git
synced 2025-03-11 03:39:23 +01:00
clarify/tighten: there is just *one* signature packet in this paragraph.
This commit is contained in:
parent
029e517b84
commit
ad7b58ce71
1 changed files with 1 additions and 1 deletions
|
@ -25,7 +25,7 @@ OpenPGP data signatures use one of two [signature types](signature_types):
|
|||
- [**Binary signature**](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#sigtype-binary) (type ID `0x00`): This is the standard signature type for binary data and is typically used for files or data streams. Binary signatures are calculated over the data without any modifications or transformations.
|
||||
- [**Text signature**](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-signature-of-a-canonical-te) (type ID `0x01`): Used for textual data, such as email bodies. When calculating a text signature, the data is first normalized by converting line endings into a canonical form (`<CR><LF>`). This mitigates issues caused by platform-specific text encodings, which is important for detached and cleartext signatures where the message file might be re-encoded between signature creation and verification.
|
||||
|
||||
Data signatures are generated by hashing the message content along with the metadata in the signature packet, and calculating a cryptographic signature over that hash. The resulting cryptographic signature is stored in an OpenPGP signature packet.
|
||||
Data signatures are generated by hashing the message content along with the metadata in the OpenPGP signature packet, and calculating a cryptographic signature over that hash. The resulting cryptographic signature is stored in the signature packet.
|
||||
|
||||
Data signature packets manifest in three distinct forms, which will be detailed in the subsequent section.
|
||||
|
||||
|
|
Loading…
Reference in a new issue