[
https://issues.apache.org/jira/browse/SSHD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16883143#comment-16883143
]
Goldstein Lyor commented on SSHD-930:
-------------------------------------
Good point - can some kind of listener callback fix this issue ? E.g., call
some {{SessionListener}} (new) callback informing it that the client
identification is (or not) about to sent. Would this provide the implementor
some kind of hook enabling it to create the proxy tunnel so that when the
client identification *is* sent the tunnel will have been established ?
> 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]
