There is no need for password between hosts and communication based on ssh

Node1:172.16.58.1

Node2:172.16.58.3

Node1-- > node2

First generate the secret key in node1

Execute the command ssh-keygen-P''

If you ask for the saved path, you can enter directly by default.

Prompted later to save the private key as / root/.ssh/id_rsa

Save the public key as / root/.ssh/id_rsa.pub

[root@node1 ~] # ssh-keygen-P''

Generating public/private rsa key pair.

Enter file in which to save the key (/ root/.ssh/id_rsa):

Your identification has been saved in / root/.ssh/id_rsa.

Your public key has been saved in / root/.ssh/id_rsa.pub.

The key fingerprint is:

Dc:62:ba:81:ac:dd:d9:93:fa:b4:9b:21:8d:e7:98:8c root@node1.magedu.com

The key's randomart p_w_picpath is:

+-[RSA 2048]-+

| | |

| | |

| | |

|. . | |

| S. | |

|. . =. | |

| o = =. | |

| | o+% o+ |

|. E OoBo |

+-+

Pass the secret key to the node2 host

Ssh-copy-id-I. ssh / id_rsa.pub root@172.16.58.3

[root@node1 ~] # ssh-copy-id-I. ssh / id_rsa.pubroot@172.16.58.3

The authenticity of host '172.16.58.3 (172.16.58.3)' can'tbe established.

RSA key fingerprint isdb:f8:11:fa:7d:30:95:44:1b:eb:ea:89:ee:fa:a1:27.

Are you sure you want to continue connecting (yes/no)? Yes

Warning: Permanently added '172.16.58.3' (RSA) to the listof known hosts.

Root@172.16.58.3's password:

Now try logging into the machine, with "ssh'root@172.16.58.3'", and check in:

.ssh / authorized_keys

To make sure we haven't added extra keys thatyou weren't expecting.

Test whether you have successfully logged in without a password. You are not prompted for a password.

Ssh 172.16.58.3 'date';date [root@node1 ~] # ssh 172.16.58.3' date';date

Wed Dec 31 16:51:41 CST 2014

Wed Dec 31 16:52:42 CST 2014