git Gitlab在推送git用户时提示输入密码

Question

提问by swaroopsm

I installed gitlab on my servers at linode. All services of gitlab are working fantastic. I am able to login, create users, repos etc. But the problem I am facing is when I try to push a repo it prompts a password for the git user as follows:

我在 linode 的服务器上安装了 gitlab。gitlab 的所有服务都运行良好。我能够登录、创建用户、存储库等。但是我面临的问题是当我尝试推送存储库时，它会提示 git 用户的密码，如下所示：

[email protected]'s password

I have followed the instructions of installing gitlab at: https://github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.mdand have disable the login got the user git using the following line mentioned in the installation guide:

我已按照以下安装 gitlab 的说明进行操作：https: //github.com/gitlabhq/gitlabhq/blob/master/doc/install/installation.md并使用安装中提到的以下行禁用登录让用户 git指导：

sudo adduser --disabled-login --gecos 'GitLab' git

须藤 adduser --disabled-login --gecos 'GitLab' git

I am using gitlab version 6. What could be the problem?

我正在使用 gitlab 版本 6。可能是什么问题？

The output of: ssh -Tvvv [email protected]is as follows:

的输出ssh -Tvvv [email protected]如下：

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 gitlab.myserver.com [MY_IP] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/swaroop/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/swaroop/.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/swaroop/.ssh/id_rsa-cert type -1
debug1: identity file /home/swaroop/.ssh/id_dsa type -1
debug1: identity file /home/swaroop/.ssh/id_dsa-cert type -1
debug1: identity file /home/swaroop/.ssh/id_ecdsa type -1
debug1: identity file /home/swaroop/.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 "gitlab.myserver.com" from file "/home/swaroop/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/swaroop/.ssh/known_hosts:92
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],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: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],[email protected],[email protected],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,[email protected]
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,[email protected]
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[email protected],zlib
debug2: kex_parse_kexinit: none,[email protected],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,[email protected]
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,[email protected]
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-256-96,hmac-sha2-512,hmac-sha2-512-96,hmac-ripemd160,[email protected],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[email protected]
debug2: kex_parse_kexinit: none,[email protected]
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 92:57:61:35:b1:e2:16:3b:7f:ae:e7:8a:dc:0c:98:83
debug3: load_hostkeys: loading entries for host "gitlab.myserver.com" from file "/home/swaroop/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/swaroop/.ssh/known_hosts:92
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "MY_IP" from file "/home/swaroop/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/swaroop/.ssh/known_hosts:93
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'gitlab.myserver.com' is known and matches the ECDSA host key.
debug1: Found key in /home/swaroop/.ssh/known_hosts:92
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/swaroop/.ssh/id_rsa (0x7fd470589410)
debug2: key: /home/swaroop/.ssh/id_dsa ((nil))
debug2: key: /home/swaroop/.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/swaroop/.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/swaroop/.ssh/id_dsa
debug3: no such identity: /home/swaroop/.ssh/id_dsa
debug1: Trying private key: /home/swaroop/.ssh/id_ecdsa
debug3: no such identity: /home/swaroop/.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
[email protected]'s password:

Also following is the output when I run: rvmsudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

以下是我运行时的输出： rvmsudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:     Ubuntu 12.04
Current User:   git
Using RVM:  yes
RVM Version:    1.22.3
Ruby Version:   2.0.0p247
Gem Version:    2.0.7
Bundler Version:1.3.5
Rake Version:   10.1.0

GitLab information
Version:    6.0.0
Revision:   6c1c284
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        http://gitlab.myserver.com
HTTP Clone URL: http://gitlab.myserver.com/some-project.git
SSH Clone URL:  [email protected]:some-project.git
Using LDAP: no
Using Omniauth: no

GitLab Shell
Version:    1.7.0
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/bin/git

Answer 1

回答by Kgaut

I had the same problem but it was because my server only accept ssh login from users of "sshusers".

我遇到了同样的问题，但这是因为我的服务器只接受来自“sshusers”用户的 ssh 登录。

On /etc/ssh/sshd_configI had the following line :

在/etc/ssh/sshd_config我有以下行：

AllowGroups sshusers

In order to fix this issue, I added git to sshusers group:

为了解决这个问题，我将 git 添加到 sshusers 组：

$ sudo adduser git sshusers

And then it's working.

然后它的工作。

Answer 2

回答by VonC

That should only mean that:

那应该只意味着：

either the public ssh key was incorrectly registered in the user account

在用户帐户中错误地注册了公共 ssh 密钥

and/or the public/private ssh keys aren't accessible from the user account (~/.sshincorrectly protected, incorrect names different from id_rsa, id_rsa.pub, incorrect ~/.ssh/configfile).
See more, for instance, at "Git SSH authentication".

和/或无法从用户帐户访问公共/私有 ssh 密钥（~/.ssh保护不正确、名称与id_rsa、不同id_rsa.pub、~/.ssh/config文件不正确）。
例如，在“ Git SSH authentication”中查看更多信息。

The OP swaroopsm comments:

该OP swaroopsm 评论：

I solved the issue by re-installing gitlab on the server. Now all is fine.

我通过在服务器上重新安装 gitlab 解决了这个问题。现在一切都很好。

Answer 3

回答by niccolox

I had a similar problem when I set the remote repository with the HTTP URL.

当我使用 HTTP URL 设置远程存储库时，我遇到了类似的问题。

I changed it to use the SSH URL, and it worked fine:

我将其更改为使用 SSH URL，并且运行良好：

git remote set-url gitlab [email protected]:niccolox/cirm-website.git

Answer 4

回答by Stanislav Bondar

In my case, I had to add the remote repository with ssh as

就我而言，我必须使用 ssh 添加远程存储库作为

git remote add gitlab ssh://[email protected]:222/git/repo_name.git

which made gitnot request me the password again. Note the use of ssh://and port=222.

这使得git不再要求我输入密码。使用注意事项ssh://和port=222。

Answer 5

回答by dennis

On systems with SELinux enabled you should not disable SELinux as suggested in some answers.

在启用了 SELinux 的系统上，您不应按照某些答案中的建议禁用 SELinux。

To get along with the SELinux restrictions (iff they are the reason for the password prompt; check your /var/log/audit/audit.log) change the security context for gitlab:

要处理 SELinux 限制（如果它们是密码提示的原因；请检查您的/var/log/audit/audit.log）更改 gitlab 的安全上下文：

chcon -t user_home_dir_t /var/opt/gitlab/
chcon -t ssh_home_t /var/opt/gitlab/.ssh/
chcon -t ssh_home_t /var/opt/gitlab/.ssh/authorized_keys

(as suggested at the gitlab group)

（如gitlab group所建议的）

Answer 6

回答by Andy Fraley

To properly fix the selinux issues, use the following. Note that chcon is only temporary and will not survive a relabel or restorecon, so you should use semanage instead.

要正确修复 selinux 问题，请使用以下命令。请注意，chcon 只是暂时的，不会在重新标记或恢复后继续存在，因此您应该使用 semanage。

semanage fcontext -a -t user_home_dir_t "/var/opt/gitlab(/.*)?"
semanage fcontext -a -t ssh_home_t "/var/opt/gitlab/.ssh(/.*)?"
restorecon -rv /var/opt/gitlab

Answer 7

回答by pcsantana

I tried many options but no success. The only that resolved for me was osxkeychain helper

我尝试了很多选择，但没有成功。唯一为我解决的是osxkeychain helper

See the tutorial here.

请参阅此处的教程。

The tutorial is from github, but works great for gitlab too.

本教程来自 github，但也适用于 gitlab。

Answer 8

回答by Jaepyoung

I had same issue. Mine was that SELinux was enabled. Please disabled SELinux here is the link http://www.how2centos.com/disable-selinux-centos-6/

我有同样的问题。我的是启用了 SELinux。请禁用 SELinux 这里是链接 http://www.how2centos.com/disable-selinux-centos-6/

git Gitlab在推送git用户时提示输入密码

提问by swaroopsm

回答by Kgaut

回答by VonC

回答by niccolox

回答by Stanislav Bondar

回答by dennis

回答by Andy Fraley

回答by pcsantana

回答by Jaepyoung

相关推荐

最近更新

标签

git Gitlab在推送git用户时提示输入密码

提问by swaroopsm

回答by Kgaut

回答by VonC

回答by niccolox

回答by Stanislav Bondar

回答by dennis

回答by Andy Fraley

回答by pcsantana

回答by Jaepyoung

相关推荐

在 Git 中，origin/master 与 origin master 之间有什么区别？

git credential.helper=cache 永远不会忘记密码？

git MAC 上的 GitBash

git 为不同的存储库设置不同的配置

相关推荐

最近更新

标签