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

Move "best practices" section down, write a minimal text

Browse source
This commit is contained in:
Heiko Schaefer 2023-12-02 21:13:25 +01:00
parent af44cc65ca
commit 32566e4bb0
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB
1 changed files with 16 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

25
book/source/05-private.md
View file

@ -223,14 +223,6 @@ In addition to key management, a keystore often involves various supplementary f
- **User interaction alerts**: Keystores might also need to prompt users for necessary interactions during certain operations. For example, OpenPGP cards may require user touch confirmation to authorize each cryptographic action.
### TSKs: Best practices S2K + S2K migration?
```{admonition} TODO
:class: warning
write
```
### Understanding key overwriting (KO) attacks
#### What they are
@ -249,4 +241,19 @@ Note that while S2K usage mode 253 (AEAD) has been introduced in the OpenPGP ver
#### Resources
For comprehensive information on KO attacks, including background, attack vectors, countermeasures, and technical analyses, visit [KOpenPGP.com](https://www.kopenpgp.com/). It is based on the paper "Victory by KO: Attacking OpenPGP Using Key Overwriting" written by Lara Bruseghini, Daniel Huigens, and Kenneth G. Paterson for the Proceedings of ACM Conference on Computer and Communications Security, Los Angeles, November 2022.
For comprehensive information on KO attacks, including background, attack vectors, countermeasures, and technical analyses, visit [KOpenPGP.com](https://www.kopenpgp.com/). It is based on the paper "Victory by KO: Attacking OpenPGP Using Key Overwriting" written by Lara Bruseghini, Daniel Huigens, and Kenneth G. Paterson for the Proceedings of ACM Conference on Computer and Communications Security, Los Angeles, November 2022.
(s2k_best_practice)=
### TSKs: Best practices S2K + S2K migration?
The RFC [recommends](https://www.ietf.org/archive/id/draft-ietf-openpgp-crypto-refresh-10.html#name-avoiding-ciphertext-malleab) that: "Users should migrate to AEAD with all due speed."
In the context of this chapter, this means that encrypted private keys should be upgraded by the user's OpenPGP software to use S2K usage mode 253 (AEAD) to encrypt the user's private key material.
Note that S2K usage mode 253 (AEAD) can be applied to both version 6 and version 4 private keys, with sufficiently up-to-date OpenPGP software. This S2K usage mode is strongly recommended for all private keys.
```{admonition} TODO
:class: warning
Can we make more specific recommendations, e.g. on how to do that?
```