ci: codespell fix

This commit is contained in:
Heiko Schaefer 2023-11-26 14:56:21 +01:00
parent 98ec25786e
commit 1b33c10bf5
No known key found for this signature in database
GPG key ID: DAE9A9050FCCF1EB

View file

@ -183,7 +183,7 @@ Preferences are sourced from signatures on different components, depending on ho
``` ```
If the user wants to write an email as "Bob", it should consider the signature on "Bob", so SHA256 should be used as hash algorithm. If the user wants to write an email as "Bob", it should consider the signature on "Bob", so SHA256 should be used as hash algorithm.
If instead the user wants to write as "Bobby", the impementation should inspect the self-certification on "Bobby" instead. If instead the user wants to write as "Bobby", the implementation should inspect the self-certification on "Bobby" instead.
However, since this signature does not carry any hash algorithm preferences subpacket, the implementation must fall back to the direct key signature instead. However, since this signature does not carry any hash algorithm preferences subpacket, the implementation must fall back to the direct key signature instead.
The same is true, if the certificate is used without any User ID as sender. The same is true, if the certificate is used without any User ID as sender.