From f1f8e6be43fb74287e777b158493b21751817206 Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Sun, 10 Dec 2023 23:26:29 +0100 Subject: [PATCH] drop duplicate advanced section --- book/source/10-encryption.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/book/source/10-encryption.md b/book/source/10-encryption.md index 87adc37..d8ac4c5 100644 --- a/book/source/10-encryption.md +++ b/book/source/10-encryption.md @@ -165,15 +165,6 @@ In this scenario, it is important that the sender encrypts the message to all av Each implementation should define a "minimum" level of security when it comes to algorithms and key lengths. If the lowest common denominator of symmetric encryption algorithms preferred by a set of recipients provides too little security, the implementation should either use a configured fallback algorithm instead, or fail to produce a message at all. -### Implications of how a recipient cert is "addressed" (fingerprint/key-ID vs. user-ID) (preferences, expiration, revocation) - -```{admonition} TODO -:class: warning - -This has been described elsewhere already. -See 9.7.3 -``` - ### AEAD modes in v2 SEIPD: GCM ```{admonition} TODO