You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Ken Diep (JIRA)" <ji...@apache.org> on 2012/05/29 23:06:24 UTC
[jira] [Created] (SSHD-171) ScpCommand block indefinately when
using the "-p" flag
Ken Diep created SSHD-171:
-----------------------------
Summary: ScpCommand block indefinately when using the "-p" flag
Key: SSHD-171
URL: https://issues.apache.org/jira/browse/SSHD-171
Project: MINA SSHD
Issue Type: Bug
Affects Versions: 0.6.0
Reporter: Ken Diep
When "-p" is specified to preserve the file mode, modification time and access time it will cause ScpCommand.java to hang indefinately. This is aside to not supporting the flag entirely.
When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) never return because of the in.read() @ line 430.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SSHD-171) ScpCommand block indefinately when
using the "-p" flag
Posted by "Ken Diep (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SSHD-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285812#comment-13285812 ]
Ken Diep commented on SSHD-171:
-------------------------------
attach a patch that will acknowledge the incoming "T<mtime> 0 <atime> 0".
> ScpCommand block indefinately when using the "-p" flag
> ------------------------------------------------------
>
> Key: SSHD-171
> URL: https://issues.apache.org/jira/browse/SSHD-171
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Ken Diep
> Attachments: SSHD-171.patch
>
>
> When "-p" is specified to preserve the file mode, modification time and access time it will cause a scp client to hang indefinately because the T header is never acknowledged. This is aside from not supporting the flag entirely.
> When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) and return -1. This causes the scp client (from cygwin and linux) to hang because it was never acknowledged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SSHD-171) ScpCommand block indefinately when
using the "-p" flag
Posted by "Ken Diep (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SSHD-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Diep updated SSHD-171:
--------------------------
Attachment: SSHD-171.patch
> ScpCommand block indefinately when using the "-p" flag
> ------------------------------------------------------
>
> Key: SSHD-171
> URL: https://issues.apache.org/jira/browse/SSHD-171
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Ken Diep
> Attachments: SSHD-171.patch
>
>
> When "-p" is specified to preserve the file mode, modification time and access time it will cause ScpCommand.java to hang indefinately. This is aside to not supporting the flag entirely.
> When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) never return because of the in.read() @ line 430.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SSHD-171) ScpCommand block indefinately when
using the "-p" flag
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SSHD-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved SSHD-171.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Assignee: Guillaume Nodet
> ScpCommand block indefinately when using the "-p" flag
> ------------------------------------------------------
>
> Key: SSHD-171
> URL: https://issues.apache.org/jira/browse/SSHD-171
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Ken Diep
> Assignee: Guillaume Nodet
> Fix For: 0.7.0
>
> Attachments: SSHD-171.patch
>
>
> When "-p" is specified to preserve the file mode, modification time and access time it will cause a scp client to hang indefinately because the T header is never acknowledged. This is aside from not supporting the flag entirely.
> When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) and return -1. This causes the scp client (from cygwin and linux) to hang because it was never acknowledged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SSHD-171) ScpCommand block indefinately when
using the "-p" flag
Posted by "Ken Diep (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SSHD-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ken Diep updated SSHD-171:
--------------------------
Description:
When "-p" is specified to preserve the file mode, modification time and access time it will cause a scp client to hang indefinately because the T header is never acknowledged. This is aside from not supporting the flag entirely.
When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) and return -1. This causes the scp client (from cygwin and linux) to hang because it was never acknowledged.
was:
When "-p" is specified to preserve the file mode, modification time and access time it will cause ScpCommand.java to hang indefinately. This is aside to not supporting the flag entirely.
When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) never return because of the in.read() @ line 430.
> ScpCommand block indefinately when using the "-p" flag
> ------------------------------------------------------
>
> Key: SSHD-171
> URL: https://issues.apache.org/jira/browse/SSHD-171
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.6.0
> Reporter: Ken Diep
> Attachments: SSHD-171.patch
>
>
> When "-p" is specified to preserve the file mode, modification time and access time it will cause a scp client to hang indefinately because the T header is never acknowledged. This is aside from not supporting the flag entirely.
> When it is specified the "T<mtime> 0 <atime> 0" is sent first, followed by the usual Cmmmm <length> <filename>. The switch statement @ line 148 never dealt with the T coming in, as a result, it will keep continuing reading the data and eventually readAck(true) and return -1. This causes the scp client (from cygwin and linux) to hang because it was never acknowledged.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira