summaryrefslogtreecommitdiffhomepage
path: root/sites
diff options
context:
space:
mode:
authorJeff Forcier <jeff@bitprophet.org>2018-09-18 14:36:54 -0700
committerJeff Forcier <jeff@bitprophet.org>2018-09-18 14:36:54 -0700
commitf17f8954e844c03fda6f785ee02ec36ed465bc05 (patch)
tree991e28db661546bea48a118aca8b0514d8bf576d /sites
parentdc82971c1af0d147433c948dc440ffabdc276a7c (diff)
parent1157252f8c4e94d5aebad02a620c6abf983055e1 (diff)
Merge branch '2.1' into 2.2
Diffstat (limited to 'sites')
-rw-r--r--sites/www/changelog.rst14
1 files changed, 14 insertions, 0 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst
index 071328f3..d924d1af 100644
--- a/sites/www/changelog.rst
+++ b/sites/www/changelog.rst
@@ -2,6 +2,20 @@
Changelog
=========
+- :support:`1292 backported` Backport changes from :issue:`979` (added in
+ Paramiko 2.3) to Paramiko 2.0-2.2, using duck-typing to preserve backwards
+ compatibility. This allows these older versions to use newer Cryptography
+ sign/verify APIs when available, without requiring them (as is the case with
+ Paramiko 2.3+).
+
+ Practically speaking, this change prevents spamming of
+ ``CryptographyDeprecationWarning`` notices which pop up in the above scenario
+ (older Paramiko, newer Cryptography).
+
+ .. note::
+ This is a no-op for Paramiko 2.3+, which have required newer Cryptography
+ releases since they were released.
+
- :support:`1291 backported` Backport pytest support and application of the
``black`` code formatter (both of which previously only existed in the 2.4
branch and above) to everything 2.0 and newer. This makes back/forward