diff options
| author | Jeff Forcier <jeff@bitprophet.org> | 2023-01-16 20:48:13 -0500 |
|---|---|---|
| committer | Jeff Forcier <jeff@bitprophet.org> | 2023-01-16 20:49:29 -0500 |
| commit | 53460723a6ab342129ac456ef6a4ba5ef676b577 (patch) | |
| tree | 718fb15f6d6147ab05ebf898bb8f3534cc1dc981 /sites | |
| parent | dfaee46c5f256d11c7b6e9ffec2e4e3f7af721fe (diff) | |
| download | paramiko-53460723a6ab342129ac456ef6a4ba5ef676b577.tar.gz | |
Stop stripping ProxyCommand none, make it None
Also apparently the old, old test for this had the wrong issue number in
it :(
Diffstat (limited to 'sites')
| -rw-r--r-- | sites/www/changelog.rst | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst index 443f0b78..6df416a0 100644 --- a/sites/www/changelog.rst +++ b/sites/www/changelog.rst @@ -2,6 +2,17 @@ Changelog ========= +- :support:`732` (also re: :issue:`630`) `~paramiko.config.SSHConfig` used to + straight-up delete the ``proxycommand`` key from config lookup results when + the source config said ``ProxyCommand none``. This has been altered to + preserve the key and give it the Python value ``None``, thus making the + Python representation more in line with the source config file. + + .. warning:: + This change is backwards incompatible if you were relying on the old (1.x, + 2.x) behavior for some reason (eg assuming all ``proxycommand`` values were + valid). + - :support:`-` The behavior of private key classes' (ie anything inheriting from `~paramiko.pkey.PKey`) private key writing methods used to perform a manual, extra ``chmod`` call after writing. This hasn't been strictly |