diff options
| author | Jeff Forcier <jeff@bitprophet.org> | 2022-01-08 13:43:50 -0500 |
|---|---|---|
| committer | Jeff Forcier <jeff@bitprophet.org> | 2022-01-08 13:43:50 -0500 |
| commit | 6699d35ad2d13fb74280a193e2e284a4a45f6f68 (patch) | |
| tree | a3f0e9f24e2def4fa8c7a3b996af1a97e61d33b3 /sites | |
| parent | 5f222495b5a62f3a1c465292bcace15888f40515 (diff) | |
Fix up logging and exception handling re: pubkey auth and presence/lack of server-sig-algs
Re #1961
Diffstat (limited to 'sites')
| -rw-r--r-- | sites/www/changelog.rst | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/sites/www/changelog.rst b/sites/www/changelog.rst index ef7ed367..61a92acb 100644 --- a/sites/www/changelog.rst +++ b/sites/www/changelog.rst @@ -2,6 +2,13 @@ Changelog ========= +- :bug:`-` Connecting to servers which support ``server-sig-algs`` but which + have no overlap between that list and what a Paramiko client supports, now + raise an exception instead of defaulting to ``rsa-sha2-512`` (since the use + of ``server-sig-algs`` allows us to know what the server supports). +- :bug:`-` Enhanced log output when connecting to servers that do not support + ``server-sig-algs`` extensions, making the new-as-of-2.9 defaulting to SHA2 + pubkey algorithms more obvious when it kicks in. - :release:`2.9.1 <2021-12-24>` - :bug:`1955` Server-side support for ``rsa-sha2-256`` and ``ssh-rsa`` wasn't fully operable after 2.9.0's release (signatures for RSA pubkeys were always |