Secure FTP (FTP over SSH)
Remote SSH server with SFTP capability.
Naming convention used: URL with sftp:// prefix, example: sftp://server.domain.com/folder1/folder2/file.ext
Extended naming convention adds port, auth data: sftp://userid

assword@server.domain.com

ort/folder/file
Authentication data is always required, and it comes in two different varieties:
* UserID + Password.
Just like in FTP, UserID and Password are required to log in.
* UserID + Private Key File.
Private Key File is a small (1-2 Kb) file that contains the "private key" part of the Public - Private Key Pair.
The Public Key is located on the server and only server administrator can put it there.
Private Key may additionally be protected by a password. Enter this password into the Browse dialog or use private key caching program such as Pageant.
We recommend to use SFTP over FTP whenever possible because:
* SFTP encrypts UserID and Password it sends to server, so listener-in-between stealing of authentication data is not possible. FTP sends UserID and Password unencrypted.
* SFTP encrypts all files that it transfers. FTP sends files as is, unencrypted.