You can authenticate SSH2 connections with a certificate (public key) just like SSL.
Send the Public key to the SSH2 server administrator.
From the Deva xFTP menu, select Tools > Options.
Select SSH2 Security.
In the right pane, select the Use public key authentication check box.
Type the path or browse to your public and private keys in the Public key path and Private key path boxes.
In the Use Passphrase box, enter your passphrase for the key.
In the Confirm passphrase box, re-enter your passphrase.
Click OK.
Your private key and passphrase are never transmitted over a connection. When the server attempts to authenticate:
The server encrypts a random number with your public key and sends it to you.
If you have not entered your passphrase in SSH2 security settings, Deva xFTP asks you for your passphrase to activate the private key.
The private key decrypts the number and sends it back to the server.
The server recognizes the number as correct and allows the connection.
To use public key authentication, you must send your public key to the server administrator before making an SSH2 connection. If the server is running OpenSSH, you must 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:
Word count should return a "1" as the first number. OpenSSH asks for the identity files password the first time you log in. If Deva xFTP fails to connect, contact our support team and provide the kernel version, OpenSSH build, and the Deva xFTP Professional build number (located under Help > About).