summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2018-09-18 21:14:40 -0700
committerJeff Forcier <jeff@bitprophet.org>2018-09-18 21:14:40 -0700
commit37aa5bce89db08769dc733ac46c49b8172533449 (patch)
treec985a495760c3c67d85c70382ac875a87a4a0bdb
parent4308ac00911754f4944b14efbfe4b677a7e92900 (diff)
parent6b406d15152e4fa144aceec67a0084ecc067dde0 (diff)
Merge branch '2.2' into 2.3
-rw-r--r--sites/www/changelog.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst
index 6e0a107e..78a89416 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -2,15 +2,16 @@
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
scenarios (usually those involving Paramiko on both ends).
-- :bug:`1283 (1.17+)` Fix exploit (CVE pending) in Paramiko's server mode
- (**not** client mode) where hostile clients could trick the server into
- thinking they were authenticated without actually submitting valid
- authentication.
+- :bug:`1283` Fix exploit (CVE pending) in Paramiko's server mode (**not**
+ client mode) where hostile clients could trick the server into thinking they
+ were authenticated without actually submitting valid authentication.
Specifically, steps have been taken to start separating client and server
related message types in the message handling tables within ``Transport`` and