Skip to content

Identification string should be sent before waiting for server identification string #505

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
martinprikryl opened this issue Jan 3, 2019 · 4 comments

Comments

@martinprikryl
Copy link

martinprikryl commented Jan 3, 2019

According to RFC 4253 Section 4.2. Protocol Version Exchange:

When the connection has been established, both sides MUST send an identification string.

SSH.NET sends its identification string only after waiting for server's identification string. Amazon Managed SFTP server has the same issue. So you cannot connect to that SFTP server with SSH.NET. Both sides first wait for the other side to send the identification string before sending its own.

Spotted thanks to: https://stackoverflow.com/q/54014749/850848

@BrainBacon
Copy link

Wow, this is exactly the same problem we are having. Going to report a bug to Amazon myself too.

@martinprikryl martinprikryl changed the title Identification string should be sent before waiting to server identification string Identification string should be sent before waiting for server identification string Jan 15, 2019
@psaffrey-origami
Copy link

We are also experiencing this issue. @BrainBacon - did you file a bug with Amazon? Can you link it?

@denispakizh
Copy link

denispakizh commented Nov 2, 2019

The same issue is with KEY EXCHANGE INIT message, library waits for the server's KEY EXCHANGE INIT message while it should not:

Key exchange (kex) begins by each side sending name-lists of supported algorithms.

https://tools.ietf.org/html/rfc4253#section-7

@drieseng drieseng added this to the 2020.0.0-beta1 milestone Jun 27, 2020
@drieseng
Copy link
Member

This is fixed in 2020.0.0-beta1.

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

5 participants