-
Notifications
You must be signed in to change notification settings - Fork 141
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
key-based authentication doesn't work with Paramiko >= 2.8.0 #399
Comments
Hello! Unfortunately, I was unable to replicate the proposed issue. As you can see in the photo (see attached photo below), by using Paramiko 2.9.2, I was able to authenticate with the identity file. Please let me know if you found any problems in my attempt to replicate the issue or if I misunderstood the problem. |
Hi, I think I'm having the same problem. I came back to some old code I was using last year, I'm sure that I used to be able to log in with the Login command, password set to None and the 'look_for_keys' option set to true. This is failing with the following information:
The Login With Public Key keyword and manually specifying the key also fails, giving this:
|
Going by what @PapaPaule said, I tried going back to Paramiko 2.7.1 and it works perfectly with that version. |
One possible cause for keys not working with 2.9.0+ while working with 2.7.1 is change to support
IIRC for some reason 2.8 does not work either, but cannot tell from changelog why. So maybe the remote server does not support server-sig-algs, i.e. uses legacy
|
no it's conn.connect('host', username='user', pkey=pkey, disabled_algorithms={'pubkeys': ['rsa-sha2-256', 'rsa-sha2-512']}) |
I ran into this issue today when trying to use SSHLibrary to log into some servers using a ECDSA-CERT key in a ssh-agent using:
The only thing that unblocked me was to downgrade to paramiko 2.7.1. |
I cannot get the keyword "Login with Public Key" working with Paramiko >= 2.8.0. If switching back to Paramiko==2.7.1 it works perfectly.
The text was updated successfully, but these errors were encountered: