-
Notifications
You must be signed in to change notification settings - Fork 664
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
Same algorithms, incompatibility between 0.4.15 and 0.5.0 #428
Comments
Can you generate an unused key that exhibits the same behavior that I can use for testing? |
Sure, here is a freshly generated key that I've verified reproduces the issue: Private Key
Pubkey
Also, here is my server's sshd_config:
My cygwin sshd is: |
I also just verified that the 0.5.0 version works fine when I use an RSA key instead of DSA. |
Hello, I got clientside: I got in system console: |
I was able to reproduce this with the given key and the problem should be fixed now with |
@thomsavage @Jacques44 Does this work for you now? |
I was able to verify that this is now fixed with current ssh2 |
@thomsavage Excellent! Thanks for the feedback. |
Trying to upgrade to the 0.5.0 release from 0.4.15 and my public-key auth connections are failing with:
{ [Error: All configured authentication methods failed] level: 'client-authentication' }
I compared all of the algorithm selections negotiated between the working (0.4.15) run to verify that they are negotiated to the same selections in the failing (0.5.0) run.
My keypair was generated as DSA.
Here is the working (0.4.15) debug output:
Here is the failing (0.5.0) run:
I captured the sshd debug log for a failing run, and it goes a little something like this:
The text was updated successfully, but these errors were encountered: