summaryrefslogtreecommitdiffhomepage
path: root/sites/www/changelog.rst
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2018-09-18 21:18:35 -0700
committerJeff Forcier <jeff@bitprophet.org>2018-09-18 21:18:35 -0700
commit6939e953d6c23061f49cde8432b6bc827cadef3f (patch)
tree6bec1de72f08f3136d53cb1080bafbb6a197f980 /sites/www/changelog.rst
parentf61a8e8eff1b192d694d884a76f32bcecbe0abf1 (diff)
parentc2fe70eb72b7a265f8363344e06247aebe95e0c1 (diff)
Merge branch '2.2' into 2.3
Diffstat (limited to 'sites/www/changelog.rst')
-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 91ca8739..7d473b24 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -7,9 +7,9 @@ Changelog
- :release:`2.1.6 <2018-09-18>`
- :release:`2.0.9 <2018-09-18>`
- :bug:`-` Modify protocol message handling such that ``Transport`` does not
- respond to ``MSG_UNIMPLEMENTED`` with its own ``MSG_UNIMPLEMENTED`` message.
- This behavior probably didn't cause any outright errors, but it doesn't seem
- to conform to the RFCs and could cause (non-infinite) feedback loops in some
+ respond to ``MSG_UNIMPLEMENTED`` with its own ``MSG_UNIMPLEMENTED``. This
+ behavior probably didn't cause any outright errors, but it doesn't seem to
+ conform to the RFCs and could cause (non-infinite) feedback loops in some
scenarios (usually those involving Paramiko on both ends).
- :bug:`1283` Fix exploit (CVE pending) in Paramiko's server mode (**not**
client mode) where hostile clients could trick the server into thinking they