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
Did not receive identification string #5830
Comments
I suspect this is a thirdparty issue as the SSH packets sent should be exactly the same for both Mac and Windows. Is there some application firewall between the PC and the server? The log entry suggests a connection is made to the server with a different protocol than SSH. |
Replying to [comment:2 dkocher]:
I have tested it with different configurations. Even without firewalls and routers - just straight connection. The same message in the server's log file. I have tested with two different servers. I have used Windows XP SP 3 as a desktop OS. |
What is the error displayed in Cyberduck? |
Replying to [comment:5 dkocher]:
Cyberduck feels happy. It is a security flaw!!! It means that Cyberduck for Windows has hacker-like behavior. |
Can you enable debug logging and do a connection attempt? Please send the cyberduck.log located in AppData to feedback@cyberduck.ch. |
Replying to [comment:7 yla]:
Do you need this log file? Cyberduck for Windows (CfW) 4.0.2 does make this wrong connection only once.There comes the story:
That's it. The appended log file is for the first time connection causing error in the server's log file. |
I don't see a clear pattern here. Always the same identification string is sent consisting of a user agent string in the format |
Cyberduck for Windows 4.01 does not connect properly using SFTP protocol. The security log file in the server states:
(server name and IP address are changed)
Without identification stream the connection is dropped by server due to security restrictions.
From the same computer other programs like WinSCP and PuTTY makes normal connections.
There is no such problem with Cyberduck for Macintosh.
Attachments
cyberduck.log.zip
(5.2 KiB)The text was updated successfully, but these errors were encountered: