-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
"read_ssh_id" issue #422
Comments
In the second case, you're connecting to a telnet server, not SSH. |
Ah ok - but would be nice if the open_connection would cancel somehow in that case. First case is the bbs from #418 20forbeers.com:1338 |
The first one seems to work for me after the #418 fix The SSH protocol allows for random data before the ID string at the beginning, so technically it's behaving correctly. Realistically, behaviour when connecting to a non compliant server is undefined. |
Doesn't work for me - unfortunately. As a terminal I can't controlthe server - they're probably using some older openssh versions or custom ssh implementations. Test case:
Deps:
Output:
Note: doesn't change if I'm not using the altered Preferred struct. |
Ok seems to be the server side - I'll try to fix it with the sysop. TY |
It works - thank you - my users will love to get a new version :-). IcyTerm has some fans it's capable of simulating some old machines. |
After connecting "russh::client::connect" seems to get stuck or error on "russh::client::connect"
Depending on the server I get either a disconnect:
Or:
And never returns.
The text was updated successfully, but these errors were encountered: