Differences
This shows you the differences between the selected revisions of the page.
| 2005-08-11 | 2005-09-02 | ||
| remove public key par and link public_key instead (martin) | stop (martin) | ||
| Line 2: | Line 2: | ||
| ===== Server Requirements ===== | ===== Server Requirements ===== | ||
| - | Using WinSCP, it is possible to connect to a [[SSH]] (Secure Shell) server with [[protocols#sftp|SFTP]] (SSH File Transfer Protocol) or [[protocols#scp|SCP]] (Secure Copy Protocol) service, mainly to UNIX machines. SFTP is a standard part of SSH-2 package. SCP is a standard part of SSH-1 package. Both protocols can be run even on the latter SSH version. WinSCP supports both SSH-1 and SSH-2. For authentication, the user can use username and password or [[public key]] (RSA or DSA). Other supported means of authorization include TIS, Cryptocard and Keyboard-interactive. | + | Using WinSCP, it is possible to connect to a [[SSH]] (Secure Shell) server with [[protocols#sftp|SFTP]] (SSH File Transfer Protocol) or [[protocols#scp|SCP]] (Secure Copy Protocol) service, mainly to UNIX machines. SFTP is a standard part of SSH-2 package. SCP is a standard part of SSH-1 package. Both protocols can be run even on the latter SSH version. WinSCP supports both SSH-1 and SSH-2. For authentication, the user can use user name and password or [[public key]] (RSA or DSA). Other supported means of authorization include TIS, Cryptocard and Keyboard-interactive. |
| &screenshotpict(login_ssh) | &screenshotpict(login_ssh) | ||
| Line 25: | Line 25: | ||
| ===== Using WinSCP with Restricted Shell Environments ===== | ===== Using WinSCP with Restricted Shell Environments ===== | ||
| - | A number of restricted shell enviroments exist for supporting | + | A number of restricted shell environments exist for supporting |
| SCP/SFTP only accounts. These systems restrict the user to a small | SCP/SFTP only accounts. These systems restrict the user to a small | ||
| subset of commands needed to manipulate files while denying the | subset of commands needed to manipulate files while denying the | ||
| - | ability to execute arbitrary commands. Some of these enviroments | + | ability to execute arbitrary commands. Some of these environments |
| - | create incompatabilities with WinSCP, particularly if using SCP | + | create incompatibilities with WinSCP, particularly if using SCP |
| instead of SFTP. | instead of SFTP. | ||
| ===== Configuring WinSCP Sessions ===== | ===== Configuring WinSCP Sessions ===== | ||
| - | Most shells nowadays offer options to make user experience better. Unfortunatelly many of these options makes the shell incompatible with WinSCP. | + | Most shells nowadays offer options to make user experience better. Unfortunately many of these options makes the shell incompatible with WinSCP. |
| - | This mostly affects SCP protocol. Example is colorised output on ''ls'' command that puts ANSI color sequences to the command output that WinSCP cannot parse. | + | 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. |
| - | Also SFTP protocol can be affected. Typical example is printing some message from startup scripts. WinSCP (and any other SFTP client) will attempt to parse the message as SFTP packet, which obviously fails. | + | 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. |
| - | You should configure your startup scripts to conform to non-interactive sessions (like WinSCP). Some shells calls different profile/startup 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 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. |
| ===== 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. | ||