2013-07-22 145 views
0

我知道有很多關於AWS會話的問題,我試圖利用它們,但都失敗了。AWS公開密鑰拒絕打開ssh

我有一個實例運行,並通過EC2管理控制檯提供的SSH字符串

ssh -i -v jason.pem [email protected] 

產生輸出

OpenSSH_5.9p1 Debian-5ubuntu1.1, OpenSSL 1.0.1 14 Mar 2012 
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for * 
debug1: Connecting to ec2-54-227-167-156.compute-1.amazonaws.com [54.227.167.156] port 22. 
debug1: Connection established. 
debug1: identity file jason.pem type -1 
debug1: identity file jason.pem-cert type -1 
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian- 5ubuntu1 
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH* 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr hmac-md5 none 
debug1: kex: client->server aes128-ctr hmac-md5 none 
debug1: sending SSH2_MSG_KEX_ECDH_INIT 
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY 
debug1: Server host key: ECDSA ea:b6:50:fe:49:49:90:76:03:91:21:6d:73:0e:04:d2 
debug1: Host 'ec2-54-227-167-156.compute-1.amazonaws.com' is known and matches the ECDSA host key. 
debug1: Found key in /home/jason/.ssh/known_hosts:27 
debug1: ssh_ecdsa_verify: signature correct 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug1: SSH2_MSG_NEWKEYS received 
debug1: Roaming not allowed by server 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug1: Authentications that can continue: publickey 
debug1: Trying private key: jason.pem 
debug1: read PEM private key done: type RSA 
debug1: Authentications that can continue: publickey 
debug1: No more authentication methods to try. 
Permission denied (publickey). 

我已經做了以下內容:

  • 創建新密鑰對,下載jason.pem並設置爲0400 chmod權限
  • 新增ChallengeResponseAuthentication yes到/ etc/SSH/ssh_config中

究竟發生了什麼事,爲什麼是jason.pem文件不被接受?

+0

您是否確定jason.pem可以與正在運行的實例一起使用?我不知道你可以改變正在運行的實例的密鑰對。 – asafreedman

+0

我關閉了實例,生成了一個新的密鑰並重新啓動。同樣的問題發生。 – Jason

回答

1

您實例上的公鑰與您的私鑰對不匹配。如果該實例的配置是重要的,你要保持它(我這樣說是基於這樣的事實,你關機的情況下,而不僅僅是創建一個新的):

  1. 創建一個新的密鑰對
  2. 創建AMI實例的您要訪問
  3. 從AMI使用新密鑰對
  4. 嘗試ssh到再次使用新的密鑰對下載
創建一個新的實例

400權限應爲f密鑰對。