Changes between Initial Version and Version 8 of Ticket #1442


Ignore:
Timestamp:
2011-07-29T18:11:14Z (13 years ago)
Author:
davidsarah
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1442

    • Property Status changed from new to assigned
    • Property Summary changed from scp fails silently when copying from a Tahoe SFTP frontend; it should fail loudly to scp fails silently when copying to a Tahoe SFTP frontend; it should fail loudly
    • Property Keywords review-needed added
    • Property Milestone changed from undecided to 1.9.0
    • Property Owner changed from davidsarah to kevan

  • Ticket #1442 – Description

    initial v8  
    1 Our SFTP frontend does not support {{{scp}}}, which is fine ({{{scp}}} tries to open a shell over the SSH connection, rather than using SFTP, and the set of commands that it can issue to that shell is not well-defined).
     1Our SFTP frontend does not support {{{scp}}}, which is fine ({{{scp}}} tries to open a shell over the SSH connection, rather than using SFTP, and ~~the set of commands that it can issue to that shell is not well-defined~~ we don't implement [http://blogs.oracle.com/janp/entry/how_the_scp_protocol_works the protocol it uses]).
    22
    33However, it isn't fine that it fails silently. This is probably a bug in {{{scp}}} rather than Tahoe, since Tahoe ''does'' report an error to the client when it tries to open a shell or issue unknown commands: lines 1873 and 1888 [source:src/allmydata/frontends/sftpd.py@4999#L1857 here]. (We need to accept shell connections in order to support the {{{df}}} command used by sshfs.) We ''might'' be able to get {{{scp}}} to fail loudly by reporting a different error, though.