[
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
