Differences
This shows you the differences between the selected revisions of the page.
| requirements 2007-04-19 | requirements 2024-11-22 12:26 (current) | ||
| Line 1: | Line 1: | ||
| ====== WinSCP Technical Requirements ====== | ====== WinSCP Technical Requirements ====== | ||
| - | ===== 伺服器需求 ===== | + | ===== Server Requirements ===== |
| - | 您可以利用 WinSCP 連線到一台 [[SSH]] (Secure Shell) 伺服器使用它的 [[protocols#sftp|SFTP]] (SSH File Transfer Protocol) 或 [[protocols#scp|SCP]] (Secure Copy Protocol) 服務；也可以利用 WinSCP 連線到一台 [[protocols#ftp|FTP]] (File Transfer Protocol) 伺服器。 | + | Using WinSCP, you can connect to an [[SSH]] (Secure Shell) server with [[SFTP]] (SSH File Transfer Protocol) or [[SCP]] (Secure Copy Protocol) service, to an [[FTP]] (File Transfer Protocol) server, HTTP server with WebDAV service or store system with [[S3]] protocol support. |
| - | SFTP 是 SSH-2 套件標準的其中一部分。SCP 是 SSH-1 套件標準的其中一部分。這兩者都可以在更新的 SSH 版本上被執行，而WinSCP 同時支援 SSH-1 及 SSH-2。在認證上，使用者可以透過帳號密碼的方式認證，亦可透過 [[public key]] (RSA or DSA) 方式進行認證。此外，WinSCP 還支援了其他的認證方式，例如 TLS、Cryptocard 及 Keyboard-interactive。 | + | SFTP is a standard file transfer protocol supported by most SSH servers. SCP is legacy protocol, supported mostly by OpenSSH and some other servers. For authentication, you can use user name and password or [[public key]]. Other authorization types include Keyboard-interactive, and Kerberos. |
| - | 對於 FTP，WinSCP 支援基本的 FTP 功能，但是 FTP over SSL 及壓縮傳送功能(Zlib)目前尚未支援。 | + | For FTP, both the basic unencrypted variant and [[ftps|FTPS]] are supported. Compressed transfers (Zlib) are not supported. |
| - | ===== [[sftp]] SFTP 需求 ===== | + | For WebDAV, both the basic unencrypted variant and WebDAVS are supported. Compressed transfers (Zlib) are not supported. |
| - | 對於 SFTP 來說，唯一的需求只有伺服器必須能執行 SFTP。換句話說，伺服器最好為 SSH-2 環境。如果您在 WinSCP 登錄頁面中中選擇 SFTP-only 且伺服器並沒有執行 SFTP 環境，WinSCP 將會嘗試著在常見的系統目錄下搜尋 SFTP 伺服端程式(例如''/usr/lib/sftp-server'', ''/usr/local/lib/sftp-server'')。如此一來，就可以達到在 SSH-1 環境下使用 SFTP 的目的。 | + | |
| + | ===== [[sftp]] SFTP Requirements ===== | ||
| + | For SFTP, the only requirement beyond the server requirements above is to run SFTP on the server. Most SSH servers include SFTP server. | ||
| ===== [[scp]] SCP Requirements ===== | ===== [[scp]] SCP Requirements ===== | ||
| - | To transfer files, ''scp1'' is used (it is called from within ''scp''). If only ''scp2'' is allowed on your server, check the //[[ui_login_scp#other_options|Use scp2 with scp1 compatibility]]// option on the [[ui_login_scp|SCP/Shell tab]] in the Login dialog. | + | As the SCP protocol implements file transfers only, WinSCP must use other means to implement the additional functionality (like directory listing). WinSCP uses Unix-like shell commands to do that. This in turn means that when using the SCP protocol, it can connect to servers that run Unix-like or its emulation only. |
| - | For correct functionality, it is necessary to satisfy a few conditions. The ''bash'' shell is recommended for working with WinSCP. If your default shell doesn't work with WinSCP, you can make WinSCP use [[ui_login_scp#shell|other shell]]. | + | To transfer files, ''scp1'' is used (it is called from within ''scp''). If only ''scp2'' is allowed on your server, check the //[[ui_login_scp#other_options|Use scp2 with scp1 compatibility]]// option on the //[[ui_login_scp|SCP/Shell page]]// on the Advanced Site Settings dialog. |
| - | For its operation, WinSCP needs several commands: ''alias'', ''cd'', ''chgrp'', ''chmod'', ''chown'', ''echo'', ''groups'', ''ls'', ''mkdir'', ''mv'', ''pwd'', ''scp'', ''rm'', ''ln'', ''unalias'' and ''unset''. These commands have to be placed in the path and user must have sufficient permissions to execute them. WinSCP expects "standard" behaviour of these commands. You can avoid needing these commands by not using some of WinSCP functions (''mkdir'', ''chown'', ''ln'', etc.) or by changing some configuration options (''alias'', ''groups'', ''unalias'' and ''unset''). | + | For correct functionality, you must do the following. The ''bash'' shell is recommended for working with WinSCP. If your default shell doesn't work with WinSCP, you can make WinSCP use [[ui_login_scp#shell|other shell]]. |
| - | Just after establishing the connection with server, all [[ui_login_scp#other_options|aliases on the above commands are cleared]]. This is done to avoid unexpected behaviour. | + | For its operation, WinSCP needs several commands: ''cd'', ''chgrp'', ''chmod'', ''chown'', ''echo'', ''groups'', ''ls'', ''mkdir'', ''mv'', ''pwd'', ''scp'', ''rm'', ''ln'', ''unalias'' and ''unset''. These commands have to be placed in the path and the user must have sufficient permissions to execute them. WinSCP expects "standard" behavior of these commands. You can avoid needing these commands by not using some of the WinSCP functions (''mkdir'', ''chown'', ''ln'', etc.) or by changing some configuration options (''groups'', ''unalias'' and ''unset''). |
| - | Another precondition is that the output of all commands is in English. This mostly concerns names of months in directory listings (''ls -la''). Because of this, WinSCP [[ui_login_scp#other_options|clears all user variables that govern command output]] after login. If command output also reflects some other server settings, it may be necessary to change this before WinSCP can be used. | + | Just after establishing the connection with a server, all [[ui_login_scp#other_options|aliases on the above commands are cleared]]. This helps avoid unexpected behavior. |
| - | The last necessary condition is the proper output of ''ls -la'' command, which is supposed to include file group name! If the group name is absent, it can be temporarily added using the //[[ui_login_scp#directory_listing|Alias LS to display group name]]// option on the //SCP/Shell tab// in the Login dialog. WinSCP will attempt detect support for ''%%--full-time%%'' switch of the ''ls'' command. If the detection causes you problems, you can [[ui_login_scp#directory_listing|disable]] it. | + | Another precondition is that the output of all commands be in English. This mostly concerns names of months in directory listings (''ls -la''). Because of this, WinSCP [[ui_login_scp#other_options|clears all user variables that govern command output]] after login. If command output also reflects some other server settings, it may be necessary to change this before WinSCP can be used. |
| - | ===== Using WinSCP with Restricted Shell Environments ===== | + | The last necessary condition is the proper output of the ''ls -la'' command, particularly the standard number and ordering of the columns. If the default output does not satisfy the needs of WinSCP you can use //[[ui_login_scp#directory_listing|Listing command]]// option on the //SCP/Shell page// on the Advanced Site Settings dialog to modify it. |
| + | |||
| + | WinSCP will attempt detect support for the ''%%--full-time%%'' switch of the ''ls'' command. If the detection causes you problems, you can [[ui_login_scp#directory_listing|disable]] it. | ||
| + | |||
| + | ===== [[restricted_shell]] Using WinSCP with Restricted Shell Environments ===== | ||
| A number of restricted shell environments exist for supporting | A number of restricted shell environments exist for supporting | ||
| - | SFTP/SCP only accounts. These systems restrict the user to a small | + | SFTP/SCP only accounts. These systems restrict an user to a small |
| - | subset of commands needed to manipulate files while denying the | + | subset of commands needed to manipulate files, while denying an |
| ability to execute arbitrary commands. Some of these environments | ability to execute arbitrary commands. Some of these environments | ||
| - | create incompatibilities with WinSCP, particularly if using SCP. | + | create incompatibilities with WinSCP, particularly if using %%SCP%%. |
| - | ===== Effect of Remote User Environment on WinSCP Sessions ===== | + | ===== [[remote_environment]] Effect of Remote User Environment on WinSCP Sessions ===== |
| Most shells nowadays offer options to make the user experience better. Unfortunately many of these options make 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 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 | + | This mainly affects the SCP protocol. An example is colorized output from the ''ls'' command that includes ANSI color sequences which WinSCP cannot parse. |
| - | unable to parse. | + | |
| Also, the SFTP protocol can be affected. A typical example is where some message is | Also, the SFTP protocol can be affected. A typical example is where some message is | ||
| Line 42: | Line 47: | ||
| 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. | 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]] Client Requirements ===== |
| - | WinSCP should run on any system running Windows 95 or later. WinSCP requires at most 10 Mb of free disk space. | + | WinSCP runs on Microsoft Windows XP SP2/Windows Server 2003 SP1 and newer, up to Windows 11 and Windows Server 2022. //The latest beta version// runs on Windows 7/2008 and newer only. &beta WinSCP runs both on client and server editions of Microsoft Windows. We know of no reason why WinSCP should not continue to work on future versions of Microsoft Windows. |
| + | |||
| + | The application //installer// does not run on Windows 7 without SP1/2008 R2 without SP1 and older. If you need to use WinSCP on an older version of Windows, use //Portable executables// download. | ||
| + | |||
| + | While there is 32-bit version of WinSCP available only, it runs on 64-bit editions of Microsoft Windows. | ||
| + | |||
| + | On Windows Server, WinSCP runs both in "Server with Desktop Experience" ("Server with a GUI") and "Server Core" installation options. | ||
| + | |||
| + | WinSCP also runs on [[https://www.winehq.org/|Wine]]. See [[https://appdb.winehq.org/objectManager.php?sClass=application&iId=1285|WinSCP entry on Wine AppDB]]. | ||
| + | |||
| + | WinSCP requires 40–100 MB of free disk space. | ||
| - | WinSCP also runs on Linux platforms where Crossover 4.x or later is running. Crossover is the commercial development of the Wine project. | + | We take care to make WinSCP an ==accessible== application, particularly to visually impaired people. WinSCP can be used on systems with screen readers. |