Skip to content

Allow for easier troubleshooting of protocol version exchange #751

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

Closed
drieseng opened this issue Dec 27, 2020 · 0 comments
Closed

Allow for easier troubleshooting of protocol version exchange #751

drieseng opened this issue Dec 27, 2020 · 0 comments

Comments

@drieseng
Copy link
Member

When the protocol version exchange fails, we currently do not provide any information of what data we actually received from the server. We also do not distinguish between a server that immediately closed the connection (after having received the client SSH identification string), and a server that sends something else instead of a SSH identification string.

There are two issues to fix:

  • Use a separate exception message to indicate that a server did not send any data at all.
  • Provide detailed information on the actual data received when the server did not send a valid SSH identification string.
Trekkan pushed a commit to Trekkan/SSH.NET that referenced this issue Mar 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant