armor: add some content and outline

This commit is contained in:
Heiko Schaefer 2023-09-26 12:56:56 +02:00
parent abc73e463a
commit 6d38a9cc1f
No known key found for this signature in database
GPG key ID: 4A849A1904CCBD7D

View file

@ -1,7 +1,31 @@
# ASCII Armor # ASCII Armor
``` The native format of OpenPGP data is binary.
- Why?
- CRC and [its deprecation in crypto-refresh](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-optional-checksum) However, in many use cases it is customary to use OpenPGP data in a non-binary encoding called "ASCII Armor." For example, ASCII Armored OpenPGP data is often used in email, for encrypted messages or for signatures.
OpenPGP's ASCII Armor mechanism consists of:
- A [header line](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-armor-header-line)
- [Headers](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-armor-headers) that can contain additional metadata
- The [Base64 encoded](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-base64-conversions) OpenPGP data
- An optional checksum for this data
- A ["tail line"](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-armor-tail-line) (footer) that matches the header line
## The Cleartext Signature Framework
```{admonition} TODO
:class: warning
Explain/discuss, [link](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-cleartext-signature-framewo)
- Linebreak normalization? - Linebreak normalization?
- Dash escaping
``` ```
## Advanced topics
### CRC (and its deprecation in crypto-refresh)
See https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-optional-checksum