From 3e4bdf998f5b1508322234a527e8fa432220368b Mon Sep 17 00:00:00 2001 From: Jeff Forcier Date: Mon, 18 Dec 2023 11:24:57 -0500 Subject: Changelog/comment updates --- paramiko/transport.py | 2 +- sites/www/changelog.rst | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/paramiko/transport.py b/paramiko/transport.py index 67843e31..83019170 100644 --- a/paramiko/transport.py +++ b/paramiko/transport.py @@ -2835,7 +2835,7 @@ class Transport(threading.Thread, ClosingContextManager): if not self.initial_kex_done: # this was the first key exchange # (also signal to packetizer as it sometimes wants to know this - # staus as well, eg when seqnos rollover) + # status as well, eg when seqnos rollover) self.initial_kex_done = self.packetizer._initial_kex_done = True # send an event? if self.completion_event is not None: 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 -- cgit v1.2.3