Differences
This shows you the differences between the selected revisions of the page.
| 2005-09-02 | 2005-11-20 | ||
| stop (martin) | english more idiomatic (mjb) | ||
| Line 9: | Line 9: | ||
| ===== [[sftp]] SFTP Requirements ===== | ===== [[sftp]] SFTP Requirements ===== | ||
| - | For SFTP, the only requirement beyond the server requirements above is to run SFTP on the server. It is best to run it as a SSH-2 subsystem. If you select SFTP-only on the login screen and the SFTP subsystem is not found, WinSCP will try to find the SFTP server in some common directories (''/usr/lib/sftp-server'', ''/usr/local/lib/sftp-server'', etc.). This way, it is possible to use SFTP even with SSH-1, which does not support subsystems. | + | For SFTP, the only requirement beyond the server requirements above is to run SFTP on the server. It is best to run it as a SSH-2 subsystem. If you select SFTP-only on the login screen and the SFTP subsystem is not found, WinSCP will try to find the SFTP server in some common directories (''/usr/lib/sftp-server'', ''/usr/local/lib/sftp-server'', etc.). This way, it is possible to use SFTP even with SSH-1, which does not support subsystems.· |
| ===== [[scp]] SCP Requirements ===== | ===== [[scp]] SCP Requirements ===== | ||
| Line 33: | Line 33: | ||
| ===== Configuring WinSCP Sessions ===== | ===== Configuring WinSCP Sessions ===== | ||
| - | Most shells nowadays offer options to make user experience better. Unfortunately many of these options makes the shell incompatible with WinSCP. | + | Most shells nowadays offer options to make the user experience better. Unfortunately many of these options make the shell incompatible with WinSCP. |
| - | This mostly affects SCP protocol. Example is colorized output on ''ls'' command that puts ANSI color sequences to the command output that WinSCP cannot parse. | + | This mainly affects the SCP protocol. An example is colorized output with the ''ls'' command that outputs ANSI color sequences to the command output which WinSCP is |
| + | unable to parse. | ||
| - | Also SFTP protocol can be affected. Typical example is printing some message from start-up scripts. WinSCP (and any other SFTP client) will attempt to parse the message as SFTP packet, which obviously fails. | + | Also, the SFTP protocol can be affected. A typical example is where some message is |
| + | printed from a start-up script. WinSCP (and any other SFTP client) will attempt to parse the message as an SFTP packet, which will obviously fail. | ||
| - | You should configure your start-up scripts to conform to non-interactive sessions (like WinSCP). Some shells calls different profile/start-up scripts for interactive and non-interactive sessions. You can use also some environment variables, like ''TERM'' to distinguish interactive and non-interactive sessions. | + | You should configure your start-up scripts to conform to non-interactive sessions (like WinSCP). Some shells call different profile/start-up scripts for interactive and non-interactive sessions. You can also use some environment variables, such as ''TERM'' to distinguish interactive and non-interactive sessions. |
| ===== Client Requirements ===== | ===== Client Requirements ===== | ||
| WinSCP should run on any system running Windows 95 or later. | WinSCP should run on any system running Windows 95 or later. | ||