2013-07-22 146 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密钥对。