ubuntu - Amazon EC2 RSA key 停止身份验证 - 权限被拒绝(公钥)

Question

关闭。这个问题是off-topic .它目前不接受答案。












想改进这个问题？ Update the question所以它是on-topic对于堆栈溢出。


11年前关闭。







Improve this question




直到不久前，对我们的 Ubuntu EC2 实例进行身份验证工作正常。突然间， key 被拒绝了。当我们使用 key 对创建一个新实例时，我们能够完美地连接到该实例，因此这似乎是现有实例的问题。端口 22 已打开。

从配置的角度来看有什么建议可以解决这个问题吗？关于我们如何进入盒子的任何想法？

这是 SSH 调试输出。有什么明显的不对吗？

非常感谢!

$ ssh -v -i ~/zzz.pem ubuntu@###.###.###.###
OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to ###.###.###.### [###.###.###.###] port 22.
debug1: Connection established.
debug1: identity file zzz.pem type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-6ubuntu2
debug1: match: OpenSSH_5.1p1 Debian-6ubuntu2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.2
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: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host '###.###.###.###' is known and matches the RSA host key.
debug1: Found key in /zzz/.ssh/known_hosts:18
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: /zzz/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering public key: zzz.txt
debug1: Authentications that can continue: publickey
debug1: Trying private key: zzz.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).

Answer 1

我们发现这里出了什么问题。盒子上的用户覆盖了主 ~/.ssh/authorized_keys - 他能够登录并检查该文件并重新添加主 .pem key 。