You can use Password, Public Key, or both authentication methods for SSH2 connections. Password authentication is the default.
On the menu bar, click Tools > Global Options.
Expand Security.
Click SSH2 security.
Make sure the Use password authentication check box is selected. You are using password authentication whenever the check box is selected, even if the box and check are dimmed.
Click OK.
Password authentication uses the FTP site login password for authentication, not the passphrase used to decrypt the identity file’s private key shown in the field beneath the Use password authentication checkbox.
On the menu bar, click Tools > Global Options.
Expand Security.
Click SSH2.
Select the Use public key authentication check box. You are using public key authentication whenever the check box is selected, even if the box and check are dimmed.
Click OK.
Important note
To use public key authentication, you will need to send your public key to the server administrator before making an SSH2 connection. If the server is running OpenSSH, you will need to convert the public key as described below:
Create an identity file in the client.
Send the public key (Identity.pub) to the server administrator (via FTP, e-mail, etc.)
The server administrator must convert the public key to OpenSSH, check it with wordcount, and add it to authorized_keys.
Command sequence:
ssh-keygen -i -f Identity.pub > sshpub
wc sshpub
cat sshpub > ~\.ssh\authorized_keys
Note
Wordcount should return a "1" as the first number. OpenSSH is going to ask for the identity files password the first time you log in. If CuteFTP fails to connect, please contact our support team and provide the kernel version, OpenSSH build, and the CuteFTP Professional build number (located under Help > About).