Open source software supply chain lighting plan, waiting for you>>>

Fault phenomenon:

[root@localhost .ssh]# ssh [email protected]

The authenticity of host '192.168.100.100 (192.168.100.100)' can't be established.

ECDSA key fingerprint is fb:db:01:40:52:4c:da:9d:56:43:52:a5:c0:27:5e:d2.

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

Warning: Permanently added '192.168.100.100' (ECDSA) to the list of known hosts.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: UNPROTECTED PRIVATE KEY FILE! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

Permissions 0644 for '/root/.ssh/id_rsa' are too open.

It is required that your private key files are NOT accessible by others.

This private key will be ignored.

bad permissions: ignore key: /root/.ssh/id_rsa

Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

Treatment process:

[root@localhost .ssh]# chmod 700 /root/.ssh/id_rsa

[root@localhost .ssh]# ssh [email protected]

Last login: Wed Feb 22 06:45:48 2017 from 192.168.100.205

Solution:

This means that the key file permission cannot be 06440644. The permission is too open. It requires that your key file cannot be read by other users. So now we need to modify the key file permissions. Enter Chmod 700/root /. SSH/ID on the command line_ RSA is enough. Here is/root /. SSH/ID_ “RSA” is the key file name given in warning, so you need to change it to the key file name given in your warning information

The format is as follows: Chmod permission code key file name