From 5c73827f28c30b762556bd128219b8eba106293e Mon Sep 17 00:00:00 2001 From: Heiko Schaefer Date: Mon, 27 Nov 2023 00:16:36 +0100 Subject: [PATCH] typo fix --- book/source/04-certificates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/source/04-certificates.md b/book/source/04-certificates.md index c075e5c..116b373 100644 --- a/book/source/04-certificates.md +++ b/book/source/04-certificates.md @@ -370,7 +370,7 @@ Filtering out some elements of a certificate can have different benefits: - For some workflows it's clear that the full certificate is not required. For example, email clients only need encryption, signing and certification component keys. They don't need authentication subkeys, which are used for SSH connections. - In some contexts, data can be added to certificates by third parties, e.g. by adding third-party User ID certifications on some key servers. In the worst case this can lead to ["certificate flooding"](https://dkg.fifthhorseman.net/blog/openpgp-certificate-flooding.html) which inflates the target certificate to a point where consumer software rejects the certificate completely. Filtering out elements can mitigate this. -- Sometimes, a certificate organically grows so big that the user software [has problems handing it](https://www.reddit.com/r/GnuPG/comments/bp23p4/my_key_is_too_large/). +- Sometimes, a certificate organically grows so big that the user software [has problems handling it](https://www.reddit.com/r/GnuPG/comments/bp23p4/my_key_is_too_large/). #### Elements that can be omitted as part of a minimization process