[ 
https://issues.apache.org/jira/browse/SSHD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883217#comment-16883217
 ] 

Thomas Wolf commented on SSHD-930:
----------------------------------

{quote}
can some kind of listener callback fix this issue ?
{quote}
The proxy protocol must be started in both cases (delayed client identification 
or not) at the very beginning. The client has to first negotiate with the 
_proxy_ the connection to the ssh server. Only once that request-reply protocol 
(both SOCKS and HTTP CONNECT are request-reply) has terminated with a "success" 
answer from the proxy the SSH protocol may start, be that the client sending 
its id and then the server answering with its own, or vice versa.

Client-side proxy support is not ideal as it is, but I managed to shoehorn the 
provided mechanisms into doing proper proxy connections in the JGit ssh client. 
Perhaps the simplest might be to factor out the proxy initialization from 
`sendClientIdentification()` and invoke it unconditionally in the constructor 
before starting the SSH protocol.

> Send the client version string after receiving the version string of the 
> server
> -------------------------------------------------------------------------------
>
>                 Key: SSHD-930
>                 URL: https://issues.apache.org/jira/browse/SSHD-930
>             Project: MINA SSHD
>          Issue Type: Improvement
>    Affects Versions: 2.2.0
>            Reporter: Zhenliang Su
>            Assignee: Goldstein Lyor
>            Priority: Major
>             Fix For: 2.3.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The rfc4253 does not indicate whether the ssh client must send its own 
> version number right after receiving the version number of the server.
> I have encountered a situation where mina-sshd is used to connect to cisco's 
> sshd service, sometimes it can be connected, sometimes not connected.
> Some rules are found by capturing packets. If the client sends its own 
> version number after receiving the version number of the server, it can be 
> connected. If the client sends its own version number before receiving the 
> version number of the server, then it will not be connected.
> I think, a better way is to change the SshClient code to send the version 
> number of the client right after receiving the version number of the server.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to