gitlab clone/push/pull 的 ssh 密钥疑难解答答案

【问题标题】：Troubleshooting ssh key for gitlab clone/push/pullgitlab clone/push/pull 的 ssh 密钥疑难解答
【发布时间】：2018-07-15 22:51:17
【问题描述】：

我尝试了以下解决方案，所以我为我的gitlab 帐户做了generated new ssh key，当我做ssh -v git@gitlab.com 时，我得到了Permissions denied (publickey).。

第二个解决方案是Working with non-default SSH key pair paths，所以我为此生成了新密钥，我的~/.ssh/config 看起来像这样

  # GitLab.com server                                                         
  Host gitlab.com
  RSAAuthentication yes
  IdentityFile ~/.ssh/id_rsa_gitlab.pub

这两个密钥都添加到我的gitlab 帐户中，当我尝试使用troubleshoot ssh 时： ssh -i ~/.ssh/id_rsa_gitlab.pub -p 122 git@gitlab.com 我什么都没有，从字面上看，当我在终端上输入它时，什么都没有发生，当我输入 shh -vvv git@gitlab.com 时，结果是这样的：

  OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /home/petar/.ssh/config
debug1: /home/petar/.ssh/config line 2: Applying options for gitlab.com
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "gitlab.com" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to gitlab.com [52.167.219.168] port 22.
debug1: Connection established.
debug1: identity file /home/petar/.ssh/id_rsa_gitlab.pub type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/petar/.ssh/id_rsa_gitlab.pub-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to gitlab.com:22 as 'git'
debug3: hostkeys_foreach: reading file "/home/petar/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/petar/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys from gitlab.com
debug3: order_hostkeyalgs: prefer hostkeyalgs: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,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@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: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
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@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
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: 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
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: ecdsa-sha2-nistp256
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: ecdsa-sha2-nistp256 SHA256:HbW3g8zUjNSksFbqTiUWPWg2Bq1x8xdGUrliXFzSnUw
debug3: hostkeys_foreach: reading file "/home/petar/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/petar/.ssh/known_hosts:3
debug3: load_hostkeys: loaded 1 keys from gitlab.com
debug3: hostkeys_foreach: reading file "/home/petar/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/petar/.ssh/known_hosts:4
debug3: load_hostkeys: loaded 1 keys from 52.167.219.168
debug1: Host 'gitlab.com' is known and matches the ECDSA host key.
debug1: Found key in /home/petar/.ssh/known_hosts:3
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
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /home/petar/.ssh/id_rsa_gitlab.pub (0x562dd6bb8c80), explicit, agent
debug2: key: ppilipovic84@gmail.com (0x562dd6bbde10), agent
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
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: /home/petar/.ssh/id_rsa_gitlab.pub
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
debug1: Offering RSA public key: ppilipovic84@gmail.com
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).

谁能解释一下如何解决这个问题？

【问题讨论】：

尝试使用-vvv 进行超详细输出
我做了，更新了我的问题，好像他没有找到我的钥匙，这部分 debug1: identity file /home/petar/.ssh/id_rsa_gitlab.pub type 1 debug1: key_load_public: No such file or directory 但我不明白为什么？

标签： linux git ssh gitlab

【解决方案1】：

IdentityFile 应该指向私钥，而不是公钥：

 IdentityFile ~/.ssh/id_rsa_gitlab

【讨论】：

是的，我做了eval $(ssh-agent -s) ssh-add ~/.ssh/other_id_rsa，但我仍然收到permission denied (public key)
您在所有问题中使用的所有键中的哪一个是添加到 gitlab 中的那个？请不要再生成任何密钥并使用您添加到 gitlab 中的单个密钥。
等等，我正在使用 git ~/.ssh/id_rsa_gitlab，ssh -vvv git@gitlab 的输出在问题中，我不再生成任何密钥，但我不明白为什么他没有在~/.ssh/中找到我的钥匙
它找到了两个密钥，但它们都被服务器拒绝了。这意味着它们可能未在服务器上正确配置。
hm，我刚刚将它们添加到设置中，并为它们命名，它们以ssh-rsa 开头并以== ppilipovic84@gmail.com 之类的邮件结尾，我会接受这一点，因为congif文件未配置。

【解决方案2】：

正如@Jakuje 建议的那样，我在IdentityFile 中犯了一个错误，但我也不知道这个gitlab 是在私人服务器上进行的，所以，如果你想从私人gitlab 克隆一个存储库，你需要这样做

git clone git@ip_address_of_the_server:SomeName/ProjectName.git 并且您将能够成功克隆存储库，但您首先需要将 ssh 密钥添加到您的 gitlab 配置文件中。

你也可以使用httpgit clone它，那么你需要这样做

http://server_ip_address/SomeName/ProjectName.git，系统会提示您输入username 和password。

【讨论】：