-
Notifications
You must be signed in to change notification settings - Fork 139
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
Ability to disable algorithms #439
base: master
Are you sure you want to change the base?
Conversation
ah, i merged in wrong order... i merged the removal of python 2 and jython first. Could you do the trick again and add a test if this is working? I think, we actually have test cases that fail because old algorithms are used (exactly the ones you mention). |
Yeah sure. I'll check next week and let you know :) |
Do you have a test case demonstrating how to use this feature? When i set the |
Hi! Sorry, I have been quite busy and have not had the chance to check the test cases yet. However before the merge I used them like this
I'll give it a shot now and test |
Ok, could you please add the testcase to |
Seems that with the keyfile implementation I am running to this failure. Related to #448
|
The error is misleading (coming from paramiko or even deeper). What the message actually tries to say: the username does not exist in target system. |
Okay I am getting passing tests for disabled algorithms now. The error was because the key was RSA which I had disabled as an algorithm and paramiko fallbacked to DSA? 😄 |
This pull request adds the ability to pass
disabled_algorithms
when connecting.Helped me connect to a legacy ssh server.
disabled_algorithms
are passed as a dictionary like in paramiko {'pubkeys': ['rsa-sha2-256', 'rsa-sha2-512']}This PR might need something that I am not aware of. Let me know, I can fix it!