Updated April 20, 2017
This article gives an overview of how FTP Voyager uses SSH connections and provides steps to configure SSH authentication using public/private key pairs.
All Serv-U versions
The Secure Edition of FTP Voyager supports SSH encryption. This option is enabled under the Advanced > Security menu of your FTP site profile.
When FTP Voyager uses SSH encryption, the log looks different from a traditional connection. The following is an example of an SSH login:
STATUS:> Connecting to "linux.com" on port 22.
SSH Server Version: SSH-1.99-OpenSSH_3.4p1 Debian 1:3.4p1-1
Server --> Client encryption: 192 bit aes-cbc
Client --> Server encryption: 192 bit aes-cbc
Selected public key protocol: ssh-dss Compression: NONE
STATUS:> Login successful
STATUS:> Getting current folder
Current folder: /home
STATUS:> Setting transfer mode to ASCII
STATUS:> Listing contents of: /home
Listing complete: /home
STATUS:> Resolving links
STATUS:> Resolving symbolic link: /home
STATUS:> Resolved 1 link into 1 folder and 0 files
Note: SSH encryption usually uses port 22. This can make traffic pass through firewalls easier. Verify that nothing is blocking port 22 for the connection to complete.
FTP Voyager also supports the use of a public/private key pair for SSH authentication. This method is used when connecting to Linux systems. To configure authentication using SSH keys, perform the following steps:
Note: FTP Voyager currently does not support configuration of key pairs for individual site profiles.
In FTP Voyager, you can create a public/private key pair if one has not already been issued to you.
4096from the drop-down list if your server supports it. The longer the key, the slower the transfer will be.