Skip to content
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

Closed
cyberduck opened this issue Mar 24, 2011 · 7 comments
Closed

Did not receive identification string #5830

cyberduck opened this issue Mar 24, 2011 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 24, 2011

ffb3a6f created the issue

Cyberduck for Windows 4.01 does not connect properly using SFTP protocol. The security log file in the server states:

Mar 24 00:59:09 MyServer sshd[21196]: Did not receive identification string from 192.168.1.1

(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
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 24, 2011

@dkocher commented

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.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 24, 2011

ffb3a6f commented

Replying to [comment:2 dkocher]:

.. Is there some application firewall between the PC and the server? ..

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.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 24, 2011

@dkocher commented

What is the error displayed in Cyberduck?

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 25, 2011

ffb3a6f commented

Replying to [comment:5 dkocher]:

What is the error displayed in Cyberduck?

Cyberduck feels happy. It is a security flaw!!! It means that Cyberduck for Windows has hacker-like behavior.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 25, 2011

@ylangisc commented

Can you enable debug logging and do a connection attempt? Please send the cyberduck.log located in AppData to feedback@cyberduck.ch.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 25, 2011

ffb3a6f commented

Replying to [comment:7 yla]:

.. Please send the cyberduck.log ..

Do you need this log file? Cyberduck for Windows (CfW) 4.0.2 does make this wrong connection only once.There comes the story:

  1. Install CfW 4.0.2. over CfW 4.0.1.
  2. Start CfW 4.0.2, connect to server. - Error in server log file. :(
  3. Close CfW 4.0.2.
  4. Start CfW 4.0.2, connect to server. - No more error in server log file. :)
  5. Close CfW 4.0.2.
  6. Install CfW 4.0.1. over CfW 4.0.2.
  7. Start CfW 4.0.1, connect to server. - No more error in server log file. :)
  8. Close CfW 4.0.1.
  9. Delete user preferences.
  10. Start CfW 4.0.1, connect to server. - Error in server log file. :(
  11. Close CfW 4.0.1.
  12. Start CfW 4.0.1, connect to server. - Error in server log file. :(
  13. Close CfW 4.0.1.
  14. Delete user preferences.
  15. Restore user preferences created by CfW 4.0.2.
  16. Start CfW 4.0.1, connect to server. - No more error in server log file. :)
  17. Close CfW 4.0.1.
  18. Install CfW 4.0.2. over CfW 4.0.1.
  19. Delete user preferences.
  20. Start CfW 4.0.2, connect to server. - Error in server log file. :(
  21. Close CfW 4.0.2.
  22. Start CfW 4.0.2.
  23. Start CfW 4.0.2, connect to server. - No more error in server log file. :)
  24. Close CfW 4.0.2.

That's it.

The appended log file is for the first time connection causing error in the server's log file.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 26, 2011

@dkocher commented

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/4.0.2 (Windows/7) (Intel)

Loading

@cyberduck cyberduck closed this Mar 26, 2011
@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants