vanitasvitae/openpgp-notes
1
0
Fork 0
mirror of https://codeberg.org/openpgp/notes.git synced 2025-12-05 05:01:07 +01:00
Code Issues Projects Releases Packages Wiki Activity

Minor fixes: footnote, codespell, broken link

Browse source
This commit is contained in:
Heiko Schaefer 2025-10-01 12:46:50 +02:00
parent 3ec4661835
commit a6f3c283d8
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
book/source/adv/signatures.md
View file

@ -52,4 +52,4 @@ That is:
Note that some historical version 3 signature packets may still be relevant for applications that handle old OpenPGP data[^sig-v3]. These version 3 signature packets will have been generated by version 4 keys.
[sig-v3]Version 4 signature packets were introduced in [RFC 2440](https://datatracker.ietf.org/doc/html/rfc2440#section-5.2) in 1998, which specifies that applications SHOULD generate v4 signature, however generation of v3 signature packets has remained allowed through [RFC 4880](https://www.rfc-editor.org/rfc/rfc4880.html#section-5.2).
[^sig-v3]: Version 4 signature packets were introduced in [RFC 2440](https://datatracker.ietf.org/doc/html/rfc2440#section-5.2) in 1998, which specifies that applications SHOULD generate v4 signature, however generation of v3 signature packets has remained allowed through [RFC 4880](https://www.rfc-editor.org/rfc/rfc4880.html#section-5.2).

2
book/source/encryption.md
View file

@ -35,7 +35,7 @@ Above, "plaintext" means one of:
- *signed message*.
A *signed message*, in turn, is a packet sequence that either
- resembles an *inline-signed message* (a *Literal Data* packet sandwhiched between one or more *One-Pass-Signature* and their respective *Signature* packets), or a
- resembles an *inline-signed message* (a *Literal Data* packet sandwiched between one or more *One-Pass-Signature* and their respective *Signature* packets), or a
- *prefixed-signed* message (one or more *Signature* packets followed by a single *Literal Data* packet).
```

2
book/source/migration.md
View file

@ -110,5 +110,5 @@ In conclusion, converting v4 key material to v6 to verify old signatures is not
Being able to read old messages using a converted key is also not really viable, since it is equally simple to just re-create the PKESK headers for a fresh v6 key.
```{note}
Also see <https://wiki.gnupg.org/OpenPGPEmailSummit202305Notes>
Also see <https://www.openpgp.org/community/email-summit/2023/minutes/#Historical_email_archive>
```