New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix unsupported cipher 'aes128-gcm' #2219
Comments
|
The cipher is actually called Reading through the source code, it seems like the packetizer is actually responsible for encrypting packets -- so it needs to be modified to properly use the AES-GCM ciphers and append the necessary authentication tags. |
|
While we're at it, might as well consider adding |
|
|
|
The
|
|
Pull request #2157 has been proposed. |
|
Flagging this for consideration as part of #387. |
A recent update of Scalingo (March 24th 2023) deprecated some ciphers (encryption algorithms). As a consequence, it is impossible to connect to Scalingo-hosted databases through SSH tunneling using Paramiko, as Scalingo-compatible ciphers are no longer supported by Paramiko.
To be more precise, I get next error when I try to open my SSH tunnel:
It seems Paramiko supports next ciphers:
('aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'aes128-cbc', 'aes192-cbc', 'aes256-cbc', '3des-cbc'), while Scalingo removed('aes128-ctr', 'aes192-ctr', 'aes256-ctr')to keep only('chacha20-poly1305', 'aes128-gcm'), making Scalingo not compatible with the use of paramiko.My request: is it possible to add support for the cipher 'aes128-gcm' ?
I tried to patch myself
transport.pyto add the missing cipher, with no success. I added 'aes128-gcm' inTransport._preferred_ciphersandin
Transport._cipher_info. Is there something missing ?Tests have been done using paramiko version 3.1.0, and Python 3.9.2.
The text was updated successfully, but these errors were encountered: