Differences
This shows you the differences between the selected revisions of the page.
| ui_login_sftp 2006-09-21 | ui_login_sftp 2024-09-23 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== SFTP Tab ====== | + | ====== The SFTP Page (Advanced Site Settings dialog) ====== |
| - | //SFTP tab// allows user to configure [[protocols#protocols#sftp_ssh_file_transfer_protocol|SFTP protocol]] specific options. | + | The //SFTP page// on the [[ui_login_advanced|Advanced Site Settings dialog]] allows user to configure [[sftp|SFTP protocol]] specific options. |
| &screenshotpict(login_sftp) | &screenshotpict(login_sftp) | ||
| - | ===== Protocol Options ===== | + | To reveal this page you need to select SFTP file protocol on [[ui_login|Login dialog]]. |
| - | 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 (Unicode) 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). | + | &toc_title_page_sections |
| + | |||
| + | ===== [[protocol_options]] Protocol Options ===== | ||
| + | Use //SFTP server// to specify path to SFTP server binary. Keep value //Default// to use the default SFTP server. Usually there will not be more SFTP servers to choose from. However you may find the option useful to change the way the SFTP server is launched. Particularly you may want to change user (known as ''su'').((See [[faq_su|FAQ]] for details.)) | ||
| + | |||
| + | 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. //In the latest beta version,// with the default //Auto// value, WinSCP will use the last version 6 with well known and tested SFTP servers and stable version 3 with others. 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 or if you know that your non-mainstream SFTP server has good support for a newer version. | ||
| + | |||
| + | Adhering to the SFTP specification, when changing directory, WinSCP asks the SFTP server to canonicalize the new path.((Using the ''SSH_FXP_REALPATH'' request.)) With OpenSSH (and possibly other) SFTP servers this has side effect that the symbolic links in the path are resolved, what can complicate navigation back. Some minor SFTP servers even have this functionality broken. For either of these reasons, you may want to turn the canonicalization off, by unchecking //Canonicalize paths on the server//. | ||
| + | |||
| + | By default SFTP has option //Allow SCP fallback// enabled. With the option enabled, WinSCP tries to find SFTP server and when it fails, it initiates SCP protocol. Note that, when fallback is disabled, WinSCP tries harder using non-standard methods to find the SFTP server. You can see the protocol actually used on the [[ui_fsinfo|Server and Protocol Information Dialog]]. SCP fallback cannot be combined with a custom path to SFTP server binary. | ||
| + | |||
| + | The //Use POSIX rename// enables use of OpenSSH ''posix-rename@openssh.com'' SFTP extension to rename files with POSIX semantics, instead of the standard SFTP rename. | ||
| ===== [[bugs]] Detection of Known Bugs in SFTP Servers ===== | ===== [[bugs]] 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]]. | + | The box allows you to configure the bugs WinSCP should expect to see in the [[sftp|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 mostly 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 mostly based on software version string of the SSH server, as most current SFTP servers does announce their software version strings. | ||
| Line 16: | Line 26: | ||
| WinSCP can work around the bugs of major SFTP servers only. There is many more known bugs in SFTP server implementations. Read more about [[interoperability]] with SFTP servers. | WinSCP can work around the bugs of major SFTP servers only. There is many more known bugs in SFTP server implementations. Read more about [[interoperability]] with SFTP servers. | ||
| - | ==== [[symlink]] Reverses Order of Symlink Command Arguments ==== | + | ==== [[link]] Reverses Order of Link Command Arguments ==== |
| - | The SFTP command to create a symbolic link (symlink) 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 link has two arguments: the path the link should point to and the path of the link itself. Some servers incorrectly expects the arguments in reversed order. |
| If the bug is detected, WinSCP will reverse the order of the arguments too. | If the bug is detected, WinSCP will reverse the order of the arguments too. | ||
| - | 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 for symbolic links on %%SFTP%% servers shipped with all versions of [[&openssh|OpenSSH]] (bug [[https://bugzilla.mindrot.org/show_bug.cgi?id=861|#861]]) and on [[http://www.proftpd.org/docs/contrib/mod_sftp.html|ProFTPD ''mod_sftp'' server]] (bug [[http://bugs.proftpd.org/show_bug.cgi?id=4080|#4080]]). For hard links, the bug is known on all current versions((A fix is scheduled for release.)) of %%SFTP%% servers shipped with ProFTPD ''mod_sftp'' server (bug [[http://bugs.proftpd.org/show_bug.cgi?id=4080|#4080]]). |
| ==== [[signedts]] Misinterprets File Timestamps Prior to 1970 ==== | ==== [[signedts]] Misinterprets File Timestamps Prior to 1970 ==== | ||
| Line 27: | Line 37: | ||
| This is SFTP-3 and older specific bug. SFTP-4 introduced signed 64-bit timestamps. | This is SFTP-3 and older specific bug. SFTP-4 introduced signed 64-bit timestamps. | ||
| + | |||
| + | ===== Further Reading ===== | ||
| + | |||
| + | Read more about [[ui_login|Login dialog]] and [[ui_login_advanced|Advanced Site Settings dialog]]. | ||