Ssl 尝试通过SSH连接到Google Cloud Shell时出现权限被拒绝（公钥）错误

我遵循Google Cloud Shell REST API文档，该文档显示如何使用该方法向我的Cloud Shell添加SSH公钥

我已经使用ssh-keygen生成了一个公钥/私钥对，并使用这个API成功地将公钥添加到我的云Shell中。完成此操作后，我可以通过使用方法获取显示此公钥的shell的详细信息来确认公钥是可访问的

每当我尝试使用相应的私钥SSH到我的云Shell时，我都会收到错误

权限被拒绝（publickey）。

• 我曾尝试使用相同的公钥/私钥对连接到其他服务器，效果很好，因此这将排除密钥问题
• 我尝试从多个Windows和Linux客户端连接，以排除本地文件权限的任何问题，但没有成功
• 我尝试了多个键，但得到了相同的结果

下面是我试图通过SSH从Ubuntu机器连接的输出：

ssh-i.ssh/id\u rsa-p 6000user@devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-XXXXXXXXXXXXX.cloudshell.dev-vvv

OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev" port 6000
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev [xx.xx.xx.xx] port 6000.
debug1: Connection established.
debug1: identity file .ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file .ssh/id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 Debian-10+deb9u6
debug1: match: OpenSSH_7.4p1 Debian-10+deb9u6 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev:6000 as 'user'
debug3: put_host_port: [devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev]:6000
debug3: hostkeys_foreach: reading file "/home/local_user/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/local_user/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from [devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev]:6000
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa
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: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ssh-rsa-cert-v01@openssh.com,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: hmac-md5,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: hmac-md5,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: rsa-sha2-512
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ssh-rsa SHA256:oaU6VCSAN/xtJF6bMyDpuffYo6Cqsqsv44JsJ5Z/5/4
debug3: put_host_port: [xx.xx.xx.xx]:6000
debug3: put_host_port: [devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev]:6000
debug3: hostkeys_foreach: reading file "/home/local_user/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/local_user/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from [devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev]:6000
debug3: hostkeys_foreach: reading file "/home/local_user/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /home/local_user/.ssh/known_hosts:2
debug3: load_hostkeys: loaded 1 keys from [xx.xx.xx.xx]:6000
debug1: Host '[devshell-vm-xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.cloudshell.dev]:6000' is known and matches the RSA host key.
debug1: Found key in /home/local_user/.ssh/known_hosts:1
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
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug2: key: .ssh/id_rsa (0x56066a887910), explicit
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ssh-ed25519,ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521>
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 gssapi-keyex,gssapi-with-mic,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: Offering RSA public key: .ssh/id_rsa
debug3: send_pubkey_test
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).

• 我已验证私钥没有损坏
• 我已经验证了我正在连接的用户名与cloud shell期望的用户名匹配
• 我已经验证了云Shell系统上的authorized_keys文件具有权限“rw-r-r”（结果是

  -rw-r--r--1根根根目录2584 Aug 26 12:08/etc/ssh/keys/authorized_keys

  ）

[更新]

运行以下命令，使用

alpha

SDK生成/安装SSH密钥：

gcloud components install alpha
gcloud alpha cloud-shell ssh --dry-run

然后可以使用SSH密钥文件

~/.SSH/google\u compute\u引擎

如果这样做有效，那么SSH密钥就是问题所在

[结束更新]

在调试输出的第87行和第88行：

debug3: send packet: type 50
debug3: receive packet: type 51

第87行表示“用户身份验证请求”。 第88行表示“用户身份验证失败”

SSH服务器拒绝了您的SSH密钥。

在Cloud Shell中运行此命令以查看SSHD的日志。您应该看到SSH密钥被拒绝的确切原因：

sudo grep -i ssh /var/log/auth.log

可能的问题/解决方案：

• 本地系统上的私钥已损坏
• 私钥与授权密钥中的远程系统公钥不匹配
• 用户名“user”与远程系统不匹配
• 远程系统授权密钥上的文件权限不正确（应为0644-“rw-r-r”）
• OpenSSH服务器无法读取授权密钥（缺少读取文件权限）

---

注意：确保您的私钥（.ssh/id_rsa）仅可由您读取（任何人都没有写入权限，除您之外的任何人都没有读取权限）-0400。

感谢您的建议：这些是我尝试连接时生成的日志：sshd[569]：rexec第33行：不推荐使用的选项keyreactionInterval sshd[569]：rexec第34行：不推荐的选项ServerKeyBits sshd[569]：rexec第45行：不推荐的选项RSASAuthentication sshd[569]：rexec第52行：不推荐的选项RhostsRSAAuthentication sshd[569]：重新处理配置第45行：不推荐的选项RSASAuthentication sshd[569]：重新处理配置第52行：不推荐的选项RhostsRSAAuthentication sshd[569]：错误：收到从xx.xx.xx.xx端口54590断开的连接：14:没有支持的身份验证方法可用[preauth]hd[569]：从xx.xx.xx.xx端口54590断开的连接[preauth]1）请不要将详细信息作为注释发布。很少有人会读它们。编辑您的问题，设置新信息的格式，以便我们可以轻松阅读，然后发布问题已更新的评论。2） 我给了你一个可能的问题清单。检查每个可能的问题后发布详细信息。3） 仔细检查日志文件。有一行提到公钥吗？4） 如果Cloud Shell的日志文件中没有错误消息，则您的问题可能是目录

~/.ssh

具有错误的文件权限或

~/.ssh/id\u rsa

具有错误的文件权限。感谢您提供的提示，我已更新了主要问题。在我的连接日志中，我可以看到debug1:key\u load\u public：没有这样的文件或目录，这让我觉得这可能是一个文件权限问题。将研究并更新。1）密钥\u加载\u公共-这只是一个警告，表明公钥文件不存在。由于将使用私钥，因此不需要进行身份验证。2） 我怀疑Cloud Shell是否有一个名为user的用户。用户名由Google Cloud IAM身份（成员帐户）确定，除非您只是屏蔽真实用户名。3） 发射云壳。在终端窗口中执行

gcloud auth list

。这是您的用户身份。

sudo grep -i ssh /var/log/auth.log