diff options
| author | Jeff Forcier <jeff@bitprophet.org> | 2018-09-18 14:39:08 -0700 |
|---|---|---|
| committer | Jeff Forcier <jeff@bitprophet.org> | 2018-09-18 14:39:08 -0700 |
| commit | 817b4fec82390abb0a7b7b897c452b5e2ebdde89 (patch) | |
| tree | cc813dff132211655adf150dc50318196e76343d /sites/www/changelog.rst | |
| parent | a87b98e10e644a310c6ba9cc428f396f0e3a1df9 (diff) | |
Pull in changelog re #1292
Rest of merge was resolved with '-s ours' to keep
those changes back on the old branches only.
Diffstat (limited to 'sites/www/changelog.rst')
| -rw-r--r-- | sites/www/changelog.rst | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst index 31320c91..e0bac44f 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 |