summaryrefslogtreecommitdiffhomepage
path: root/sites
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2023-12-18 11:24:57 -0500
committerJeff Forcier <jeff@bitprophet.org>2023-12-18 11:24:57 -0500
commit3e4bdf998f5b1508322234a527e8fa432220368b (patch)
treebc4e7eb85b89ad5847587bc9b7209fca25c30120 /sites
parent30b447b911c39460bbef5e7834e339c43a251316 (diff)
Changelog/comment updates
Diffstat (limited to 'sites')
-rw-r--r--sites/www/changelog.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst
index 682e3beb..9814298e 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -18,10 +18,10 @@ Changelog
the CBC ciphers (this option is present in Paramiko >=2.6).
- As the fix for the vulnerability requires both ends of the connection to
cooperate, the below changes will only take effect when the remote end is
- OpenSSH >= TK (or equivalent, such as Paramiko in server mode, as of this
- patch version) and configured to use the new "strict kex" mode. Paramiko
- will always attempt to use "strict kex" mode if offered by the server,
- unless you override this by specifying ``strict_kex=False`` in
+ OpenSSH >= 9.6 (or equivalent, such as Paramiko in server mode, as of
+ this patch version) and configured to use the new "strict kex" mode.
+ Paramiko will always attempt to use "strict kex" mode if offered by the
+ server, unless you override this by specifying ``strict_kex=False`` in
`Transport.__init__`.
- Paramiko will now raise an `SSHException` subclass (`MessageOrderError`)
when protocol messages are received in unexpected order. This includes