The authenticity of host 'ec2-54-228-137-210.cn-north-1.compute.amazonaws.com.cn (54.228.137.210)' can 't be established.
RSA key fingerprint is: 33:3 f 2 d: 74:1 d: 80:36: c9:04: e2:3 b: 99: Ed: 3 e: 45: ff.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ec2-54-228-137-210.cn-north-1.compute.amazonaws.com.cn, 54.228.137.210' (RSA) to the list of known hosts.
@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @
Permissions for 0777 'alicesso. Pem are too open.
It is It that your private key files are NOT accessible by others.
This private key will be ignored.
Bad permissions: ignore key: alicesso pem
The Enter passphrase for key 'alicesso. Pem:
Generally choose the secret key should not directly can SSH to the target host? A great god, please give directions
Permission denied (publickey).
CodePudding user response:
The building Lord have solved? Before I also appear this problem, can be connected,CodePudding user response:
Because alicesso. Pem permissions is too high, use the following command can be solved:Chmod 600 alicesso. Pem
CodePudding user response:
Puttygen generate the private key into PKK etc. If you are a Windows againCodePudding user response:
See or good extensionCodePudding user response:
The second floor method can solvePrompt also said permission is too open
Permissions for 0777 'alicesso. Pem are too open.
It is It that your private key files are NOT accessible by others.
CodePudding user response:
Looks like a permission problem