vanitasvitae/openpgp-notes
1
0
Fork 0
mirror of https://codeberg.org/openpgp/notes.git synced 2025-09-10 11:49:40 +02:00
Code Issues Projects Releases Packages Wiki Activity

Fix paragraph sliding into reference

Browse source
This commit is contained in:
Paul Schaub 2023-12-08 21:14:35 +01:00
parent 2b58f68018
commit 5e1c7efd4a
Signed by: vanitasvitae
GPG key ID: 62BEE9264BF17311
1 changed files with 1 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
book/source/15-migration.md
View file

@ -52,6 +52,7 @@ The OpenPGP v6 standard gives guidance for implementers by listing[^migration_st
Some features of OpenPGP v6 are only available for use with keys in the v6 format. Some features of OpenPGP v6 are only available for use with keys in the v6 format.
For example, only a v6 key might issue a v6 signature[^v6keyv6sig]. For example, only a v6 key might issue a v6 signature[^v6keyv6sig].
[^v6keyv6sig]: [v6 keys can only issue v6 signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-packet-versions-in-signatur) [^v6keyv6sig]: [v6 keys can only issue v6 signatures](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-packet-versions-in-signatur)
On the other hand, a v6 key can *only* issue v6 signatures, so if you require compatibility with v4 verifiers, you shouldn't yet migrate to a v6 key/certificate. On the other hand, a v6 key can *only* issue v6 signatures, so if you require compatibility with v4 verifiers, you shouldn't yet migrate to a v6 key/certificate.
When migrating to v6 key material, the user must either switch to a freshly generated v6 key, or convert their v4 keys to the v6 format. Doing the former is the recommended approach. When migrating to v6 key material, the user must either switch to a freshly generated v6 key, or convert their v4 keys to the v6 format. Doing the former is the recommended approach.