-
-
Notifications
You must be signed in to change notification settings - Fork 903
Problem connecting to bitvise WinSSHD 7.42 server #1448
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
Comments
Could you provide me the IP address to connect to the SSH server myself so that I might be able to reproduce the issue and test possible fixes? I wouldn't need any login credentials since it seems like the issue is with the key exchange process. If you'd be willing to do this you could email the info to terrafrost@php.net. Failing that I can try to install bitvise WinSSHD 7.42 myself. Thanks! |
Hi, Do you think updating bitvise could help? I could try suggesting that to the receiving side if it might solve the issue. |
I tried to connect to Bitvise SSH Server 8.39 and was able to do so without issue with phpseclib 2.0.23. I think the issue may have something to do with this:
That's NET_SSH2_MSG_KEXDH_GEX_INIT. The server should be responding with NET_SSH2_MSG_KEXDH_GEX_REPLY but it's not (the fact that the logs show UNKNOWN is actually a bug that was fixed with 500e322#diff-82a5983a6daace4acbcc65edf2dfb605) Anyway, I assume the logs following the "And sftp verbouse output" section are from different clients? Because the phpseclib logs seem to show a connection that's not being made whereas the "sftp verbouse output" appears to show a successful connection (albeit with a login failure). I mean, I will say that phpseclib doesn't support GSSAPI but that shouldn't be an issue... |
Hi, |
Hi, |
Uh oh!
There was an error while loading. Please reload this page.
I have tried both 1.x and 2.x version of this package and both result in same problem.
I can conenct with he commandline sftp client.
Code:
Log:
And sftp verbouse output:
The text was updated successfully, but these errors were encountered: