diff options
author | Muri Nicanor <muri@immerda.ch> | 2017-11-29 19:01:41 +0100 |
---|---|---|
committer | Muri Nicanor <muri@immerda.ch> | 2017-11-29 19:01:41 +0100 |
commit | 3bb1ac31649e657dad72f27fbf196c30f14efc60 (patch) | |
tree | 4ddb373971ad9e55c92603ba9fe496411e11f83f /docs | |
parent | 537395e5cb1d5b8f4563cc37abd916dca1c08aff (diff) |
Rewrite the paragraph about the pin_keys subcommand as probosed by paz
Diffstat (limited to 'docs')
-rw-r--r-- | docs/index.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/index.md b/docs/index.md index 45c8b94..46a5137 100644 --- a/docs/index.md +++ b/docs/index.md @@ -396,10 +396,11 @@ Call this command weekly from cron to automate the check and have the results se schleuder refresh_keys -Schleuder can also **pin keys**. Each subscription of each list will be checked if it has a key assigned to it. If there is no key assigned, schleuder will try to -select an encryption capable key from the lists keyring based on the email address. +If there is no key assigned, schleuder will try to select a key from the list's keyring that distinctly matches the subscription's email address. -Call this command weekly from cron to automate the check and have the results sent to the respective list-admins: +This feature should be used with care. It's easy for a malicious (or inexperienced) person to inject additional user-IDs into the list's keyring. This can lead to situations in which people suddenly receive emails that are encrypted to a key they don't own. + +You should better not run this command automatedly, and you should always examine the output closely to check for unintended consequences. schleuder pin_keys |