Activity log for bug #1973241

Date Who What changed Old value New value Message
2022-05-12 20:41:31 Dan Streetman bug added bug
2022-05-12 20:41:40 Dan Streetman nominated for series Ubuntu Jammy
2022-05-12 20:41:40 Dan Streetman bug task added paramiko (Ubuntu Jammy)
2022-05-12 20:41:40 Dan Streetman nominated for series Ubuntu Kinetic
2022-05-12 20:41:40 Dan Streetman bug task added paramiko (Ubuntu Kinetic)
2022-05-12 20:41:58 Dan Streetman bug watch added https://github.com/paramiko/paramiko/issues/2012
2022-05-12 20:41:58 Dan Streetman bug task added paramiko
2022-05-12 20:45:19 Dan Streetman description [impact] paramiko fails to connect to some servers. [test case] attempt to connect to a server that does not support server-sig-algs and also only supports ssh-rsa (specifically, does not support rsa-sha2-512). the connection will fail: DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa' DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512', 'rsa-sha2-256', 'ssh-rsa'] DEBUG:paramiko.transport:Server did not send a server-sig-algs list; defaulting to our first preferred algo ('rsa-sha2-512') DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms' SSHClient/Transport init kwarg to disable that or other algorithms if your server does not support them! INFO:paramiko.transport:Authentication (publickey) failed. Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in connect self._auth( File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth raise saved_exception File "/usr/lib/python3/dist-packages/paramiko/client.py", line 736, in _auth key = self._key_from_filepath( File "/usr/lib/python3/dist-packages/paramiko/client.py", line 588, in _key_from_filepath key = klass.from_private_key_file(key_path, password) File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 249, in from_private_key_file key = cls(filename=filename, password=password) File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 64, in __init__ self._from_private_key_file(filename, password) File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 190, in _from_private_key_file data = self._read_private_key_file("RSA", filename, password) File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 322, in _read_private_key_file data = self._read_private_key(tag, f, password) File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 351, in _read_private_key data = self._read_private_key_openssh(lines[start:end], password) File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 452, in _read_private_key_openssh raise PasswordRequiredException( paramiko.ssh_exception.PasswordRequiredException: private key file is encrypted [regression potential] any regression would likely prevent paramiko from connecting to a remote server. [scope] this needs to be fixed in jammy and later. this problem was introduced in paramiko 2.9.0 so does not exist in impish or earlier. [other info] this doesn't appear to be fixed upstream yet. https://github.com/paramiko/paramiko/issues/2012 [impact] paramiko fails to connect to some servers. [test case] attempt to connect to a server that does not support server-sig-algs and also only supports ssh-rsa (specifically, does not support rsa-sha2-512). the connection will fail: DEBUG:paramiko.transport:Finalizing pubkey algorithm for key of type 'ssh-rsa' DEBUG:paramiko.transport:Our pubkey algorithm list: ['rsa-sha2-512', 'rsa-sha2-256', 'ssh-rsa'] DEBUG:paramiko.transport:Server did not send a server-sig-algs list; defaulting to our first preferred algo ('rsa-sha2-512') DEBUG:paramiko.transport:NOTE: you may use the 'disabled_algorithms' SSHClient/Transport init kwarg to disable that or other algorithms if your server does not support them! INFO:paramiko.transport:Authentication (publickey) failed. Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/lib/python3/dist-packages/paramiko/client.py", line 435, in connect     self._auth(   File "/usr/lib/python3/dist-packages/paramiko/client.py", line 766, in _auth     raise saved_exception   File "/usr/lib/python3/dist-packages/paramiko/client.py", line 736, in _auth     key = self._key_from_filepath(   File "/usr/lib/python3/dist-packages/paramiko/client.py", line 588, in _key_from_filepath     key = klass.from_private_key_file(key_path, password)   File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 249, in from_private_key_file     key = cls(filename=filename, password=password)   File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 64, in __init__     self._from_private_key_file(filename, password)   File "/usr/lib/python3/dist-packages/paramiko/rsakey.py", line 190, in _from_private_key_file     data = self._read_private_key_file("RSA", filename, password)   File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 322, in _read_private_key_file     data = self._read_private_key(tag, f, password)   File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 351, in _read_private_key     data = self._read_private_key_openssh(lines[start:end], password)   File "/usr/lib/python3/dist-packages/paramiko/pkey.py", line 452, in _read_private_key_openssh     raise PasswordRequiredException( paramiko.ssh_exception.PasswordRequiredException: private key file is encrypted [regression potential] any regression would likely prevent paramiko from connecting to a remote server. [scope] this needs to be fixed in jammy and later. this problem was introduced in paramiko 2.9.0 so does not exist in impish or earlier. [other info] this doesn't appear to be fixed upstream yet. https://github.com/paramiko/paramiko/issues/2012 Note this can be worked around if direct access to the paramiko code is possible, by using the 'disabled_algorithms' parameter to the client connect() method, e.g.: client.connect("<hostname>", disabled_algorithms={'pubkeys': ['rsa-sha2-256', 'rsa-sha2-512']}) Note this can break connections to other systems however, that do support (only) those algs, so is not a very good workaround. Additionally, this workaround isn't even possible if paramiko is being used internally by some other python application.
2022-05-12 21:59:07 Bug Watch Updater paramiko: status Unknown New
2022-05-13 01:04:13 Haw Loeung bug added subscriber Haw Loeung
2022-08-17 03:44:45 Launchpad Janitor paramiko (Ubuntu): status New Confirmed
2022-08-17 03:44:45 Launchpad Janitor paramiko (Ubuntu Jammy): status New Confirmed