You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Goldstein Lyor (JIRA)" <ji...@apache.org> on 2017/05/26 18:04:04 UTC
[jira] [Resolved] (SSHD-749) SFTP client sends wrong open flags for
protocol version 4
[ https://issues.apache.org/jira/browse/SSHD-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Goldstein Lyor resolved SSHD-749.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Thanks for the diangosis and patch - merged with appropriate credit.
> SFTP client sends wrong open flags for protocol version 4
> ---------------------------------------------------------
>
> Key: SSHD-749
> URL: https://issues.apache.org/jira/browse/SSHD-749
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Christian Leiner
> Assignee: Goldstein Lyor
> Fix For: 1.6.0
>
> Attachments: AbstractSftpClient_open_flags.patch, SftpVersionsTest_open_flags.patch
>
>
> While trying to create a file on a remote server using {{SftpClient}}, I always received {{SSH_FX_NO_SUCH_FILE}}. However, there were no problems with the server when using another client.
> Debugging the issue, I discovered that {{AbstractSftpClient.open()}} doesn't handle the {{OpenMode}} options according to the spec when using protocol version 4 (https://tools.ietf.org/html/draft-ietf-secsh-filexfer-04) and diverges from SSHD's server implementation as well (i.e. {{SftpSubsystem.doOpen()}}).
> I have attached a test case to reproduce the problem ({{SftpVersionsTest_open_flags.patch}}). There's also a simple patch that should fix the issue ({{AbstractSftpClient_open_flags.patch}}).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)