我正在嘗試 ssh 進入我被授予所有者訪問權限的谷歌雲端實例“ajc2”。這是我正在使用的命令：
gcloud compute --project "clear-mountain-94802" ssh --zone "us-central1-c" "ajc2" --ssh-flag="-vvv"
我已經成功運行了“gcloud init”和“gcloud auth login”。
看起來 ssh 金鑰已成功生成，並且我的 .ssh 資料夾的權限設定為 700。我不確定為什麼會收到錯誤“權限被拒絕（公鑰）”。有人對此有見解嗎？
我無法將程式碼貼到 serverfault，因為它認為它是垃圾郵件，所以我連結了我在 google groups 上發布的包含程式碼的原始帖子：https://groups.google.com/forum/#!topic/gce-discussion/ex8roHMubLY
andrewfu:fwdrestartingvnc andrewfu$ pwd
/Users/andrewfu/Downloads/fwdrestartingvnc
andrewfu:fwdrestartingvnc andrewfu$ gcloud compute --project "clear-mountain-94802" ssh --zone "us-central1-c" "ajc2" --ssh-flag="-vvv"
OpenSSH_7.6p1, LibreSSL 2.6.2
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 35.232.179.72 port 22.
debug1: Connection established.
debug1: identity file /Users/andrewfu/.ssh/google_compute_engine type 0
debug1: key_load_public: No such file or directory
debug1: identity file /Users/andrewfu/.ssh/google_compute_engine-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6
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
debug3: fd 5 is O_NONBLOCK
debug1: Authenticating to 35.232.179.72:22 as 'andrewfu'
debug1: using hostkeyalias: compute.638568653107616640
debug3: hostkeys_foreach: reading file "/Users/andrewfu/.ssh/google_compute_known_hosts"
debug3: record_hostkey: found key type ECDSA in file /Users/andrewfu/.ssh/google_compute_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from compute.638568653107616640
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: curve25519-sha256,[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]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
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: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] 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: ecdsa-sha2-nistp256 SHA256:gO6j1NcV2hOFWMbe+JguVd3iqqV2c2Loo7CD+B4LgJU
debug1: using hostkeyalias: compute.638568653107616640
debug3: hostkeys_foreach: reading file "/Users/andrewfu/.ssh/google_compute_known_hosts"
debug3: record_hostkey: found key type ECDSA in file /Users/andrewfu/.ssh/google_compute_known_hosts:1
debug3: load_hostkeys: loaded 1 keys from compute.638568653107616640
debug1: Host 'compute.638568653107616640' is known and matches the ECDSA host key.
debug1: Found key in /Users/andrewfu/.ssh/google_compute_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: /Users/andrewfu/.ssh/google_compute_engine (0x7ff9f540e110), 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: Offering public key: RSA SHA256:W0uL2eaHbndzPnMB070+ZzPHHLDY2v4pgtnPRXHlpc0 /Users/andrewfu/.ssh/google_compute_engine
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.
[email protected]: Permission denied (publickey).
ERROR: (gcloud.compute.ssh) [/usr/bin/ssh] exited with return code [255].
答案1
您確定使用了正確的使用者名稱嗎？嘗試在瀏覽器視窗中使用 SSH 從 Google 控制台進行連線。連接後，請發出whoami命令以查看用戶名是什麼。然後嘗試使用完全相同的用戶名透過 ssh 連線。如果您嘗試使用不同的用戶名，則不會起作用。如果您從本機 Linux 電腦執行它，它很可能會嘗試與您的本機 Linux 使用者連接，而該使用者很可能與 Google Cloud 中 Linux 電腦上的使用者名稱不同
答案2
請注意以下命令規範中的 USER@INSTANCE：
gcloud 計算 ssh [USER@]INSTANCE [--command=COMMAND] [--container=CONTAINER] [--dry-run] [--force-key-file-overwrite] [--internal-ip] [--普通] [--ssh-flag=SSH_FLAG] [--ssh-key-file=SSH_KEY_FILE] [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] [--zone=ZONE] [GCLOUD_WIDE_FLAG …] [ ……]
我看到您只指定了“實例”部分“ajc2”，而不是 user@ajc2 ，將“user”替換為有權訪問此實例的Google用戶名，IOW，正確的用戶名
您的原始指令： gcloudcompute --project "clear-mountain-94802" ssh --zone "us-central1-c" "ajc2" --ssh-flag="-vvv"