Method 1: Use ssh-keygen(1) to generate and configure
(1) Generate a key pair
[ root@iZwz9catu2mrq92b07d1d0Z ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.//Enter file name
Enter file in which to save the key(/root/.ssh/id_rsa): keys_root
//Enter the private key encryption password
Enter passphrase(empty for no passphrase)://Enter the password again
Enter same passphrase again:
Your identification has been saved in keys_root.
Your public key has been saved in keys_root.pub.
The key fingerprint is:
f4:f9:70:51:cf:09:f6:da:30:6a:b1:67:4f:dc:14:44 root@iZwz9catu2mrq92b07d1d0Z
The key's randomart image is:+--[ RSA 2048]----+| o+E ||..ooo||...o o+||...+.*..|| S ++.++.||.+o o ||..|||||+-----------------+//The file is generated successfully, keys_root is the private key, keys_root.pub is the public key[root@iZwz9catu2mrq92b07d1d0Z ~]# ls
keys_root keys_root.pub
(2) Configure the public key
//Write the generated public key to the user's authorized_keys[root@iZwz9catu2mrq92b07d1d0Z ~]# echo -e '#this is keys_root'>>~/.ssh/authorized_keys ; cat ~/keys_root.pub >> ~/.ssh/authorized_keys
[ root@iZwz9catu2mrq92b07d1d0Z ~]# cat ~/.ssh/authorized_keys
# this is keys_root
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAyhp9SBxas8Nmwdi4dQfOuUULpMGRnGEFopU2DXhSF+PE/s80xrVS31Ycd5o4gU3iehKx2vo4OEB2lYZ2JCfptTc59HAj+Qwqh7i5S4YQuX/+31GkY+s8XKFR4QgH1ubQt9feU2cagfG1f+wWRsa0YtefE67Kjv6OZuKuA2bOdrAH4mzV1m71iLMUZYgaEnfJExXj2lbPAXRqCV+tdIj9h0jxhB5pQXsZ3NE38D22WYNKO4Sy8odfE7Oby1I0Emm8Uhiwqgx91HP22iY/WqzZOxeKZPF17CPWr9cChaPh9/DXM1Wd8KDCg33MO6hbpqAwh7iEughndXly0FY0oZNKnQ== root@iZwz9catu2mrq92b07d1d0Z
(3) Configure the private key
Download the private key to the local machine
[ root@iZwz9catu2mrq92b07d1d0Z ~]# sz keys_root
Start Xshell
Tools
User Key Manager
Import the downloaded keys_root file (Import)
Configuration complete
Method 2: Use Xshell to generate and configure
[ root@iZwz9catu2mrq92b07d1d0Z ~]# man ssh
The user creates his/her key pair by running ssh-keygen(1). This stores the private key in ~/.ssh/identity (protocol 1), ~/.ssh/id_dsa (protocol 2 DSA), ~/.ssh/id_ecdsa (protocol 2
ECDSA), or ~/.ssh/id_rsa (protocol 2 RSA) and stores the public key in ~/.ssh/identity.pub (protocol 1), ~/.ssh/id_dsa.pub (protocol 2 DSA), ~/.ssh/id_ecdsa.pub (protocol 2 ECDSA), or
~ /.ssh/id_rsa.pub (protocol 2 RSA) in the user’s home directory. The user should then copy the public key to ~/.ssh/authorized_keys in his/her home directory on the remote machine.
The authorized_keys file corresponds to the conventional ~/.rhosts file, and has one key per line, though the lines can be very long. After this, the user can log in without giving
the password.
Note: Each user has his own authorized_keys
~ /.ssh/authorized_keys
Lists the public keys (RSA/ECDSA/DSA) that can be used for logging in as this user. The format of this file is
described in the sshd(8) manual page. This file is not highly sensitive, but the recommended permissions are
read/write for the user, and not accessible by others.
Note: It is recommended that the file permissions are read and write permissions for the owner, and other users have no permissions
This article from the Chinese CentOS station - focus on Linux technology Author: [centos] (https://www.centoschina.cn/author/1) published its copyright are CentOS Chinese station - all focused on Linux technology, the content of the article the authors and do not necessarily represent CentOS Chinese station - focus on Linux technology point of view Agree or support. If you need to reprint, please indicate the source of the article.
( adsbygoogle = window.adsbygoogle || []).push({});
Recommended Posts