0

我最近对我的 gitlab 进行了备份，并将其恢复到另一台机器上。机器浏览良好，我可以创建项目和创建团队等等。

但我不能从本地机器推送到这台机器，因为它要求“git密码”。现在我知道这可能是一些身份密钥问题，所以我从服务器上删除了我用户的旧密钥并添加了新密钥，但问题仍然存在。

我尝试检查 ssh 错误但没有任何线索

  ssh -vvvT git@192.168.1.91
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 *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.1.91 [192.168.1.91] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/brij/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/brij/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/brij/.ssh/id_rsa-cert type -1
debug1: identity file /home/brij/.ssh/id_dsa type -1
debug1: identity file /home/brij/.ssh/id_dsa-cert type -1
debug1: identity file /home/brij/.ssh/id_ecdsa type -1
debug1: identity file /home/brij/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1.1
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1.1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1.1
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "192.168.1.91" from file "/home/brij/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/brij/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
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
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: 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-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: 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: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: mac_setup: found hmac-md5
debug1: kex: server->client aes128-ctr hmac-md5 none
debug2: mac_setup: found hmac-md5
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 b0:3d:ef:ee:b4:8a:cb:47:e1:f2:a2:b6:da:ad:29:e5
debug3: load_hostkeys: loading entries for host "192.168.1.91" from file "/home/brij/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/brij/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host '192.168.1.91' is known and matches the ECDSA host key.
debug1: Found key in /home/brij/.ssh/known_hosts:1
debug1: ssh_ecdsa_verify: signature correct
debug2: kex_derive_keys
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/brij/.ssh/id_rsa (0xb7a6c760)
debug2: key: /home/brij/.ssh/id_rsa (0xb7a75188)
debug2: key: /home/brij/.ssh/id_dsa ((nil))
debug2: key: /home/brij/.ssh/id_ecdsa ((nil))
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
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/brij/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Offering RSA public key: /home/brij/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/brij/.ssh/id_dsa
debug3: no such identity: /home/brij/.ssh/id_dsa
debug1: Trying private key: /home/brij/.ssh/id_ecdsa
debug3: no such identity: /home/brij/.ssh/id_ecdsa
debug2: we did not send a packet, disable method
debug3: authmethod_lookup password
debug3: remaining preferred: ,password
debug3: authmethod_is_enabled password
debug1: Next authentication method: password
git@192.168.1.91's password:

==================================================== =====

更新 - 我发现在 /home/git/.ssh 文件 authorized_keys 丢失，而它在我进行备份的另一台服务器上的同一位置可用 gitlab-shell 之间还有一个符号链接

gitlab-shell -> /opt/bitnami/apps/gitlab/gitlab-shell/

这是否与它有关。

4

2 回答 2

0

我发现在 /home/git/.ssh 文件 authorized_keys 丢失了，而它在我进行备份的另一台服务器上的同一位置可用 gitlab-shell 之间还有一个符号链接

gitlab-shell -> /opt/bitnami/apps/gitlab/gitlab-shell/

我创建了符号链接并重新启动了 gitlab 服务器。工作就像一个魅力，但对于我所有的用户，我们必须在服务器上更改他们的密钥，也许文件夹备份复制和恢复不是移动服务器的正确方法，我花了 2 天时间解决了这个问题。

更新 - 我从旧服务器复制了授权密钥，现在用户也不必更改他们的密钥。但是现在他们会被要求更改服务器身份，linux用户将不得不删除 known_hosts 文件并使用服务器的新已知主机身份重新生成它，而 Windows 用户可以正常工作，因为他们会被要求更换身份，他们只需要对它说“是”。

于 2013-11-13T12:18:29.697 回答
0

因为您没有明确提及，所以我不确定您是否备份和恢复 SSH 密钥。一般来说，你应该备份你的~/.ssh/id_rsa（私钥）和~/.ssh/id_rsa.pub（公钥）文件，否则你需要重新生成SSH密钥并上传到Gitlab服务器。

你提到：

我从服务器中删除了我用户的旧密钥并添加了新密钥，但问题仍然存在。

详细地说，这意味着您应该：

  • 用于ssh-keygen重新生成密钥对（默认为~/.ssh/id_rsaand ~/.ssh/id_rsa.pub）。
  • 上传~/.ssh/id_rsa.pub到 Gitlab 服务器。

如果您认为您确实这样做了，您可以使用以下说明仔细检查所有内容：

  1. 用于ssh-keygen -y -f ~/.ssh/id_rsa从您的公钥重新生成私钥。
  2. 检查步骤 1 生成的密钥是否与您的~/.ssh/id_rsa.pub密钥相同（电子邮件无关紧要）。如果它们不同，则重新生成密钥对并上传到 Gitlab 服务器。
  3. 检查 Gitlab 上的公钥是否与步骤 1 和 2 中的密钥相同。

通常，经过这些检查后，SSH 密钥应该可以正常工作。

于 2013-11-13T06:34:58.840 回答