Buttoned at the customer site, a domestic platform, when configuring the machine trust discovery, A may be exempted from close access B, B can not be free and confidential access to A, B can not be free and secret access B, were following several treatment.
1) determine the directory permissions:
/ root / 755
/root/.ssh 700
/root/.ssh/authorized_keys 600
2) After the public being given sign_and_send_pubkey: signing failed: agent refused operation solution
at this time we just executed under
eval "$ (SSH-Agent -s)"
SSH-the Add
3) using ssh ip cat /root/.ssh/id_rsa.pub >> authorized_keys 600 may change the key, comes tool preferably used, performed, respectively, on both sides
ssh-copy-id -i root @ distal ip id_rsa.pub
The final configuration is successful trust
Previous method:
. 1) RSA ssh-keygen -t
2) is then input into the local content id_rsa.pub authorized_keys and
3) and the distal end to the inside of the machine through ssh cat manner
4) and finally distributed to the individual machines
But this has given rise to a visit to another successful, the other a visit Shique to enter a password, it is best to use ssh-copy-id to pass.