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

normalize term: password->passphrase

Browse source
This commit is contained in:
Heiko Schaefer 2023-12-11 02:01:49 +01:00
parent 07c68cd0e3
commit 07dc692b2b
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
book/source/10-encryption.md
View file

@ -66,7 +66,7 @@ Encrypted session key (ESK) packets are a family of two mechanisms for securing
- [PKESK](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-public-key-encrypted-sessio): Uses asymmetric OpenPGP key material to protect a session key, and
- [SKESK](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-12.html#name-symmetric-key-encrypted-ses): Uses passphrases to protect the symmetric key material, instead of OpenPGP asymmetric key material (this is less commonly used).
An arbitrary number of PKESKs and SKESKs can be used in the same message. It is also possible to mix the two, resulting in a message which can be decrypted using either one of the designated OpenPGP keys or any of the passwords used to encrypt the message. This is useful to make a message available to a number of known recipients, with the option to provide the password to future recipients.
An arbitrary number of PKESKs and SKESKs can be used in the same message. It is also possible to mix the two, resulting in a message which can be decrypted using either one of the designated OpenPGP keys or any of the passphrases used to encrypt the message. This is useful to make a message available to a number of known recipients, with the option to provide the passphrase to future recipients.
### PKESK: Session key encrypted to an asymmetric OpenPGP key

2
book/source/11-decryption.md
View file

@ -31,7 +31,7 @@ Once any of these methods succeeded, the resulting *session key* is used to decr
- using revoked subkey?
```
## Password-protected session key (SKESK)
## Passphrase-protected session key (SKESK)
Decrypting a SKESK packet to recover the *session key* is done by performing the encryption steps in reverse, based on a user-provided passphrase.