Authoritative guide to ssh password-less Login
[0] PrefaceBecause ssh implements password-free login, the general steps are as follows:0.1)The client logs on to the server through ssh;0.2)Server checks the. ssh file in the home directory, and sends the public key file authorized_keys to the client;0.3)The client receives the public key file from the server, parses it with its own private key file, and calculates the new public key file C;0.4)The server segment receives the client's public key file C and matches it with its own public key file (it has its own matching algorithm, you don't care). If the matching succeeds, the client successfully logs on to the server;(Attention ):
Here, we have to say that the process of establishing an ssh password-free login is really complicated. Therefore, ssh requires strict access to the configuration file. If you are a friend, you will not be able to establish password-free login Based on the access permissions set in this article, the consequence is at your own risk (Here we only want to emphasize that ssh requires strict access to the configuration file! (Just because the access permission to your configuration file is not completely correct, ssh has never been able to achieve normal password-free login, which is very effort-consuming)[1] Install ssh
server installation :sudo yum -y install openssh.i686client installation: sudo yum -y install openssh-clients
[2] My task: hadoop @ hadoop0 (Client) password-free login to hadoop @ hadoop1 (Server)
2.1) generate the private key and public key for creating ssh (client operation)
Attention)
A1) <喎?http: www.bkjia.com kf ware vc " target="_blank" class="keylink"> Vc3Ryb25nPiB + Ly5zc2gvIMS/examples/ycTcu + examples/downloads/ra8yse3 + examples/samples + PC9wPg0KPHA + samples/samples" write the image description here "src =" http://www.bkjia.com/uploads/allimg/150902/0409524614-1.png "title =" \ "/> 2.3) Upload the client's public key file data to the server (client operation)
2.4) change the public key file name under the. ssh folder of the server to authorized_keys, and change the access permission to 600 or 644 (server operation) 2.5) client login to the server without Password