-
Notifications
You must be signed in to change notification settings - Fork 9
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
Doesn't seem to work with Ubuntu 22 #130
Comments
I think this is due to using an RSA key - the original protocol for signing with the RSA key is to use sha1, but that's frowned upon now, and disabled by default in openssh on ubuntu-22.04. There's a new way to sign using sha-256 or sha-512, I haven't added this feature to paramiko-ng yet, but it was added to paramiko-2.9.0. |
Thank you! There's no rough estimate when this might be fixed, right?
(I thought this workaround might work, but seems the problem here varies slightly -- https://askubuntu.com/questions/1404049/ssh-without-password-does-not-work-after-upgrading-from-18-04-to-22-04)
|
Considering that I haven't really done any work on this project in the last 6 months, that's a good assumption :) but who knows, maybe I'll get back into it now ... |
So, funny thing, I ran I assume fab-classic isn't fully compatible with paramiko and will break in some odd ways, but it's smooth sailing so far. |
fab-classic should be pretty much fully compatible with original/upstream paramiko, and there's even a trick to making it explicitly depend on original/upstream paramiko instead of paramiko-ng if you need to install it again: PARAMIKO_REPLACE=1 pip install --no-binary fab-classic (mentioned in https://github.com/ploxiln/fab-classic#install) (But it is usually necessary to uninstall paramiko or paramiko-ng before switching to the other, otherwise things are silently mixed-up, so it's good you did that :) |
The following gives me
AuthenticationException
with paramiko-ng, while it works fine with paramiko-2.11.0.The host is runs Ubuntu 22. Pointing to an Ubuntu 20 server resolves.
The text was updated successfully, but these errors were encountered: