Differences
This shows you the differences between the selected revisions of the page.
| 2005-01-27 | 2005-05-05 | ||
| "login dialog" removed from title (martin) | 3.7.5 sftp version, utf, timestamps (1970) (martin) | ||
| Line 1: | Line 1: | ||
| ====== SFTP Tab ====== | ====== SFTP Tab ====== | ||
| - | //SFTP tab// allows you to configure the bugs WinSCP should expect to see in the [[protocols|SFTP server]]. | + | //SFTP tab// allows user to configure [[protocols#protocols#sftp_ssh_file_transfer_protocol|SFTP protocol]] specific options.· |
| &screenshotpict(login_sftp) | &screenshotpict(login_sftp) | ||
| + | |||
| + | ===== Protocol Options ===== | ||
| + | Use //Preferred SFTP protocol version// to configure maximal version of SFTP protocol that WinSCP will attempt to use. WinSCP will seamlessly downgrade to any lower version that the server supports. The only reason, that you may want to change the option for, is bug either in SFTP server or WinSCP itself specific to particular version of the protocol. | ||
| + | |||
| + | Use //Server does not use UTF-8// to configure if WinSCP should use UTF-8 encoding for filenames in communication with the server. With default //Auto// value, UTF-8 will be used for SFTP protocol 4 and newer, unless the server is known not to support UTF-8 (Foxit software WAC Server). Set the option to //On// to unconditionally disable usage of UTF-8. Set the option to //Off// to force usage of UTF-8 (useful for servers using MBCS natively). | ||
| + | |||
| + | ===== Detection of Known Bugs in SFTP Servers ===== | ||
| + | The box allows you to configure the bugs WinSCP should expect to see in the [[protocols#protocols#sftp_ssh_file_transfer_protocol|SFTP server]]. | ||
| Each bug can be configured in three states. With //Off// WinSCP will assume that the server does not have the bug. With //On// WinSCP will assume that the server does have the bug. With //Auto// (default) WinSCP will try to guess whether or not the server has the bug. The guessing is based on software version string of the SSH server, as most current SFTP servers does announce their software version strings. | Each bug can be configured in three states. With //Off// WinSCP will assume that the server does not have the bug. With //On// WinSCP will assume that the server does have the bug. With //Auto// (default) WinSCP will try to guess whether or not the server has the bug. The guessing is based on software version string of the SSH server, as most current SFTP servers does announce their software version strings. | ||
| - | ===== Reverses Order of Symlink Command Arguments ===== | + | ==== Reverses Order of Symlink Command Arguments ==== |
| The SFTP command to create a symbolic link has two arguments: the path the symbolic link should point to and the path of the symlink itself. Some servers incorrectly expects the arguments in reversed order. | The SFTP command to create a symbolic link has two arguments: the path the symbolic link should point to and the path of the symlink itself. Some servers incorrectly expects the arguments in reversed order. | ||
| Line 13: | Line 21: | ||
| The bug is known on SFTP servers shipped with all versions of [[&openssh|OpenSSH]] (bug [[http://bugzilla.mindrot.org/show_bug.cgi?id=861|#861]]). | The bug is known on SFTP servers shipped with all versions of [[&openssh|OpenSSH]] (bug [[http://bugzilla.mindrot.org/show_bug.cgi?id=861|#861]]). | ||
| - | ===== Does Not Use UTF-8 for SFTP4 and Never ===== | + | ==== Misinterprets File Timestamps Prior to 1970 ==== |
| - | Since version 4 of SFTP protocol all filenames must be encoded using UTF-8. Some servers fail to fulfil the requirement. | + | While specification for SFTP protocol version 3 and older defines file timestamp to be unsigned 32-bit number representing number of seconds from Jan 1, 1970 in UTC, at least OpenSSH interprets it as signed number. The result is that files on the server with timestamps before 1970 will be interpreted by WinSCP as times after 2038. As it is probably quite common bug, it is currently considered to apply for all servers. Set the option to //Off// if it does not for your server. |
| - | + | ||
| - | If the bug is detected, WinSCP stops using UTF-8 to encode filenames and will not decode incoming filenames from UTF-8. | + | |
| - | + | ||
| - | The bug is known on SFTP servers shipped with all versions of Foxit software WAC Server. | + | |
| + | This is SFTP-3 and older specific bug. SFTP-4 introduced signed 64-bit timestamps. | ||