2017-02-15 15 views
0

Я хочу ssh к моей амазонке ec2, но всегда показывает разрешение отказа (publickey).Amazon ec2 show «Разрешение отказано (publickey)»

 
ssh -i "tsaohucn.pem" [email protected] -vvv 

Это отладочная информация.

 
OpenSSH_7.3p1, LibreSSL 2.4.1 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 20: Applying options for * 
debug2: resolving "ec2-54-213-252-182.us-west-2.compute.amazonaws.com" port 22 
debug2: ssh_connect_direct: needpriv 0 
debug1: Connecting to ec2-54-213-252-182.us-west-2.compute.amazonaws.com [54.213.252.182] port 22. 
debug1: Connection established. 
debug1: key_load_public: No such file or directory 
debug1: identity file tsaohucn.pem type -1 
debug1: key_load_public: No such file or directory 
debug1: identity file tsaohucn.pem-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_7.3 
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000 
debug2: fd 3 setting O_NONBLOCK 
debug1: Authenticating to ec2-54-213-252-182.us-west-2.compute.amazonaws.com:22 as 'ubuntu' 
debug3: hostkeys_foreach: reading file "/Users/kaogaau/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /Users/kaogaau/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from ec2-54-213-252-182.us-west-2.compute.amazonaws.com 
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521 
debug3: send packet: type 20 
debug1: SSH2_MSG_KEXINIT sent 
debug3: receive packet: type 20 
debug1: SSH2_MSG_KEXINIT received 
debug2: local client KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c 
debug2: host key algorithms: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa 
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 
debug2: compression ctos: none,[email protected],zlib 
debug2: compression stoc: none,[email protected],zlib 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal 
debug2: KEX algorithms: [email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 
debug2: host key algorithms: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519 
debug2: ciphers ctos: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[email protected],[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: ciphers stoc: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[email protected],[email protected],[email protected],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[email protected] 
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-sha1,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-md5,hmac-sha1,[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96 
debug2: compression ctos: none,[email protected] 
debug2: compression stoc: none,[email protected] 
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: [email protected] 
debug1: kex: host key algorithm: ecdsa-sha2-nistp256 
debug1: kex: server->client cipher: [email protected] MAC: compression: none 
debug1: kex: client->server cipher: [email protected] MAC: compression: none 
debug3: send packet: type 30 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug3: receive packet: type 31 
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:w9ILtc0o/o2k0qd3FSHXyiP9x9uPVnUWEYuuFr21Ft4 
debug3: hostkeys_foreach: reading file "/Users/kaogaau/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /Users/kaogaau/.ssh/known_hosts:3 
debug3: load_hostkeys: loaded 1 keys from ec2-54-213-252-182.us-west-2.compute.amazonaws.com 
debug3: hostkeys_foreach: reading file "/Users/kaogaau/.ssh/known_hosts" 
debug3: record_hostkey: found key type ECDSA in file /Users/kaogaau/.ssh/known_hosts:2 
debug3: load_hostkeys: loaded 1 keys from 54.213.252.182 
debug1: Host 'ec2-54-213-252-182.us-west-2.compute.amazonaws.com' is known and matches the ECDSA host key. 
debug1: Found key in /Users/kaogaau/.ssh/known_hosts:3 
debug3: send packet: type 21 
debug2: set_newkeys: mode 1 
debug1: rekey after 134217728 blocks 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug3: receive packet: type 21 
debug2: set_newkeys: mode 0 
debug1: rekey after 134217728 blocks 
debug1: SSH2_MSG_NEWKEYS received 
debug2: key: tsaohucn.pem (0x0), explicit 
debug3: send packet: type 5 
debug3: receive packet: type 6 
debug2: service_accept: ssh-userauth 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug3: send packet: type 50 
debug3: receive packet: type 51 
debug1: Authentications that can continue: publickey 
debug3: start over, passed a different list publickey 
debug3: preferred publickey,keyboard-interactive,password 
debug3: authmethod_lookup publickey 
debug3: remaining preferred: keyboard-interactive,password 
debug3: authmethod_is_enabled publickey 
debug1: Next authentication method: publickey 
debug1: Trying private key: tsaohucn.pem 
debug3: sign_and_send_pubkey: RSA SHA256:dcqlb/XKI3QtFZkQgarVwizp0n3p46C3TtcWNMxGlgw 
debug3: send packet: type 50 
debug2: we sent a publickey packet, wait for reply 
debug3: receive packet: type 51 
debug1: Authentications that can continue: publickey 
debug2: we did not send a packet, disable method 
debug1: No more authentication methods to try. 
Permission denied (publickey). 

Кто-нибудь знает, что случилось?

+0

Что такое разрешение 'tsaohucn.pem' файла? – franklinsijo

+0

sudo chmod 400 tsaohucn.pem – Tsao

ответ

1

Причины отказа в выдаче экземпляра EC2.

  1. При запуске в EC2 экземпляр, вы должны выбрать подсеть и должны включить публичный IP в разделе Работа в сети.
  2. Вам необходимо открыть порт 22 в Входящее правило группы безопасности и открыть общедоступный IP-адрес вашей машины для доступа к экземпляру.
  3. Удостоверяются, что интернет-шлюз был подключен к публичной подсети, где был запущен экземпляр EC2.
0

Я воссоздаю новые экземпляры ec2 и новые пары ключей, и он работает. Я не знаю почему, но, возможно, амазонка приносит некоторые ошибки, когда я использовал старые пары ключей.