-
-
Notifications
You must be signed in to change notification settings - Fork 932
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
Send the client key exchange init in Connect #1274
Conversation
I will check this next week. |
Can we prepare tests to cover two cases? When does server initialization occur and when does it not? |
Added a unit test for when the server does not send kexinit edit:
The RFC says "Key exchange (kex) begins by each side sending name-lists of supported algorithms." I.e. there is no indication that the client or server should wait for the other. SSH.NET currently waits for the server to send its supported algorithms. This works OK against most server implementations, but if the server is waiting for SSH.NET, then we have a problem. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
The 2023.0.1 version has been released to Nuget: https://www.nuget.org/packages/SSH.NET/2023.0.1 |
After discussion in #972, I have been running this in production against several different servers for a week or so.
An example key exchange with this change:
And an example when the server init comes in first:
cc @geoffstewart