[
https://issues.apache.org/jira/browse/SSHD-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17652427#comment-17652427
]
Roberto Deandrea commented on SSHD-1318:
----------------------------------------
Hi Thomas
Thank you for your prompt reply.
We found a workaround for this issue, so I don't change the code at all.
I don't know which is the partner SFTP server. The banner received is
"SSH-2.0-SFTP-SERVER"
Regards
Roberto
> Question about SSHD-1204
> ------------------------
>
> Key: SSHD-1318
> URL: https://issues.apache.org/jira/browse/SSHD-1318
> Project: MINA SSHD
> Issue Type: Question
> Affects Versions: 2.8.0
> Reporter: Roberto Deandrea
> Priority: Minor
>
> Hi Thomas,
> I have a SSHD client 2.8.0 connecting to a SFTP server which identifies
> itself with this banner *SSH-2.0-SFTP Server.*
> The SFTP client fails to authenticate with the following error:
> _Caused by: org.apache.sshd.common.SshException:
> DefaultAuthFuture[ssh-connection]: Failed (StreamCorruptedException) to
> execute: Incorrect identification (null characters not allowed) - at line 1
> character #1 after ''_
> This is the symptom described in SSHD-1204.
> The problem described in SSHD-1204 was solved with a workaround, i.e. setting
> {color:#242424}*org.apache.sshd.send-immediate-kex-init=false* for the SFTP
> client.{color}
>
> {color:#242424}Q. Do you think is safe setting
> {color:#242424}*org.apache.sshd.send-immediate-kex-init=false* for every SFTP
> client ; are you aware of any side effects ?{color}{color}
>
> {color:#242424}{color:#242424}{color:#242424}{color:#242424}Thank you in
> advance{color}{color}{color}{color}
> {color:#242424}{color:#242424}Kind Regards{color}{color}
>
> {color:#242424}{color:#242424}Roberto{color}{color}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org
For additional commands, e-mail: dev-h...@mina.apache.org
