2014-06-12 147 views
1

我在CentOS 6盒子上安裝了全新的gitlab-omnibus,我已正確配置它並可以訪問Web界面,但我添加了我的SSH密鑰,但是當我嘗試Git克隆一個新安裝的倉庫,我需要通過SSH爲Git用戶提供一個密碼。我用三臺不同的機器和三個不同的帳戶嘗試過這種方式,但問題仍然存在。GitLab SSH請求密碼並忽略SSH密鑰

這裏是一個冗長的SSH輸出

╭─[email protected] ~ 
╰─$ ssh -vT [email protected]                                          130 ↵ 
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 
debug1: Reading configuration data /etc/ssh_config 
debug1: /etc/ssh_config line 20: Applying options for * 
debug1: Connecting to gitlab [37.26.93.221] port 22. 
debug1: Connection established. 
debug1: identity file /Users/jacobclark/.ssh/id_rsa type 1 
debug1: identity file /Users/jacobclark/.ssh/id_rsa-cert type -1 
debug1: identity file /Users/jacobclark/.ssh/id_dsa type -1 
debug1: identity file /Users/jacobclark/.ssh/id_dsa-cert type -1 
debug1: Enabling compatibility mode for protocol 2.0 
debug1: Local version string SSH-2.0-OpenSSH_6.2 
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 
debug1: match: OpenSSH_5.3 pat OpenSSH_5* 
debug1: SSH2_MSG_KEXINIT sent 
debug1: SSH2_MSG_KEXINIT received 
debug1: kex: server->client aes128-ctr hmac-md5 none 
debug1: kex: client->server aes128-ctr hmac-md5 none 
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP 
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent 
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY 
debug1: Server host key: RSA a1:62:aa:51:0c:20:f3:3e:10:17:c7:20:a4:0b:7b:16 
debug1: Host 'gitlab.' is known and matches the RSA host key. 
debug1: Found key in /Users/jacobclark/.ssh/known_hosts:1 
debug1: ssh_rsa_verify: signature correct 
debug1: SSH2_MSG_NEWKEYS sent 
debug1: expecting SSH2_MSG_NEWKEYS 
debug1: SSH2_MSG_NEWKEYS received 
debug1: Roaming not allowed by server 
debug1: SSH2_MSG_SERVICE_REQUEST sent 
debug1: SSH2_MSG_SERVICE_ACCEPT received 
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /Users/jacobclark/.ssh/id_rsa 
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password 
debug1: Trying private key: /Users/jacobclark/.ssh/id_dsa 
debug1: Next authentication method: password 
[email protected]'s password: 
+0

請問http://stackoverflow.com/a/17740432/6309的幫助?或者https://github.com/gitlabhq/gitlabhq/issues/3384?或http://serverfault.com/a/555021/783? – VonC

+0

服務器的認證/等等。日誌說當你嘗試連接?服務器上該用戶的.ssh目錄(以及其中的文件)有哪些權限? –

+0

您是否通過GitLab web界面添加SSH密鑰?還是你將它添加到authorized_keys unix風格? – jvanbaarsen

回答

1

您需要關閉SELinux的:setenforce 0

1

我在CentOS完全相同的問題,原來是由於Centrify公司正在使用管理ssh密鑰,這是非標準的,但是我們企業服務器管理流程的一部分。

我對Centrify不太熟悉,因爲它由另一個團隊管理,但是我通過從gitlab授權密鑰文件創建了一個sym鏈接到/ etc/sshd/auth-keys/git來解決了這個問題。

的authorizedkeys文件值給我的符號鏈接需要去的位置,與sshd -T

造成這種解決我的問題來確定:

ln -s /var/opt/gitlab/.ssh/authorized_keys /etc/ssh/auth-keys/git