mirror of
https://codeberg.org/openpgp/notes.git
synced 2024-11-23 08:02:05 +01:00
armor: add some content and outline
This commit is contained in:
parent
abc73e463a
commit
6d38a9cc1f
1 changed files with 28 additions and 4 deletions
|
@ -1,7 +1,31 @@
|
|||
# ASCII Armor
|
||||
|
||||
```
|
||||
- Why?
|
||||
- CRC and [its deprecation in crypto-refresh](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-optional-checksum)
|
||||
The native format of OpenPGP data is binary.
|
||||
|
||||
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?
|
||||
```
|
||||
- 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
|
||||
|
|
Loading…
Reference in a new issue