Are you still using Putty + WinSCP/FileZilla?
Then we recommend looking into software like xShell.
- It supports not only the SSH protocol but also others, such as telnet or rlogin.
- You can connect to multiple servers simultaneously (tabbed interface).
- No need to enter your credentials each time; they can be saved.
- Starting from version 6, it features a Russian interface and supports all Russian encodings, including UTF-8.
- It supports both password and key-based connections.
- Moreover, you no longer need to launch WinSCP or FileZilla separately for file management via ftp/sftp.
- The developers of xShell have anticipated your needs and also created xFtp, which supports standard FTP and SFTP.
- Most importantly, xFtp can be launched directly from an active SSH session and will immediately connect to that specific server in file transfer mode (using the sFtp protocol). However, you can also open xFtp independently and connect to any of the servers.
A key pair generator and a key management tool are also included.
Completely free for personal non-commercial use or for educational purposes.
Fill in the required fields, especially the email, to which you have access; a download link will be sent there.
Download and install both applications. Launch them.
After launching, you will see a window with a list of saved sessions; it will be empty for now. Click ‘New.’
Fill in the connection details: port/host/IP address, as well as the desired session name.
Next, go to authentication and enter your login credentials with the password.
Then click OK and connect to the server.
The same applies for xFTP. The only thing to choose is the protocol; by default, it will be sFTP, but you can select regular FTP.
One of the most convenient features is that selected text is automatically copied to the clipboard.
(Tools - Options - Keyboard and Mouse - Copy selected text to clipboard).
You can connect not only using a password but also by using a key, which is much safer and more convenient.
You need to generate your key, or more precisely, a pair of public/private keys.
Run Xagent (installed with the package).
You will see a list of keys, which will be empty at first. Click Manage Keys, then Generate.
Type RSA.
Length at least 4096 bits.
Click Next, wait. Then click Next again.
Name the key as you wish, and if desired, you can secure the key by setting an additional password (this will be requested when connecting or importing the key on another device).
Next, we see our PUBLIC key. We use it to connect to the server. One key can be used on many servers, which is convenient.
The generation is complete, but that's not all.
You need to add the key on the server.
Connect to the server via ssh and navigate to /root/.ssh.
root@alexhost# cd /root/.ssh to which we often receive an error -bash: cd: /root/.ssh: No such file or directory.
This is normal; this folder is missing if keys have not been generated on the server before.
You also need to generate the server's own key in a similar way.
root@alexhost# ssh-keygen -t rsa -b 4096 We will be prompted for a path to save the key file.
We agree to the default /root/.ssh/id_rsa by pressing Enter.
Next, enter a password for the key file and confirm it, or leave it blank and press Enter.
Again, go to /root/.ssh:
root@alexhost# cd /root/.sshYou need to create the authorized_keys file:
root@alexhost# nano authorized_keysPaste our key in text form that we obtained earlier:
Save and exit.
Ctrl + O
Ctrl + X
Go to xShell, call up the list of saved sessions (Alt+O).
Find our session, click properties, and go to authentication.
In the method field, select public key.
In the user key field, choose our previously created key, save, and connect.
The client uses the PRIVATE key, and the PUBLIC key is specified on the server.
The private key can be transferred to another PC of yours if you want to connect from it.
In Xagent — manage keys, select the key — Export, and save it.
On another PC, in Xagent — manage keys — Import, select and add it. If the key was password protected, the password will be requested at this moment.
The key can be specified for any user, not just root.
The standard path is /home_user_folder/.ssh/authorized_keys.
For the user alexhost, for example, by default this will be /home/alexhost/.ssh/authorized_keys.
Source: habr.com
