summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2022-02-11 13:04:33 -0500
committerJeff Forcier <jeff@bitprophet.org>2022-02-11 13:04:33 -0500
commitc9a3409b6d4078b77167467feafe5f102ec53671 (patch)
tree2a9cea50e653c55acf7aa3974d57c8924c37719b
parent88f35a537428e430f7f26eee8026715e357b55d6 (diff)
Clarify disabled algorithms keys vs pubkeys in changelog
-rw-r--r--sites/www/changelog.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst
index 460089fe..0b1bd9fe 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -51,9 +51,9 @@ Changelog
cert, will act as follows:
- In all cases, the list of algorithms to consider is based on the new
- ``preferred_pubkeys`` list (see below) and ``disabled_algorithms``; this
- list, like with host keys, prefers SHA2-512, SHA2-256 and SHA1, in that
- order.
+ ``preferred_pubkeys`` list (see below) and ``disabled_algorithms``
+ (specifically, its ``pubkeys`` key); this list, like with host keys,
+ prefers SHA2-512, SHA2-256 and SHA1, in that order.
- When the server does not send ``server-sig-algs``, Paramiko will attempt
the first algorithm in the above list. Clients connecting to legacy
servers should thus use ``disabled_algorithms`` to turn off SHA2.