2016-03-22 24 views
5

先週から私のコマンドラインgitが動作していません。私が覚えているのは、gitバージョンのローカルフォルダを制御してリモートgit refを追加することです。それから私のgitはプッシュまたはプルすることができません。それは示しています。奇妙な何Gitlab - gitの認証に失敗しました

git clone [email protected]:xxx/myproj.git myproj 
Cloning into 'myproj'... 
Received disconnect from 192.168.xxx.xxx: 2: Too many authentication failures for git 
fatal: Could not read from remote repository. 

Please make sure you have the correct access rights 
and the repository exists. 

がJetBrainアイデアの私のバージョンコントロールが正常に動作し、それはまだコマンドラインで引くことができないプロジェクトを取得またはプッシュできるということです。

これまでにid_rsa.pubをgitlabに追加しましたが、もう一度追加し直しても動作しません。

私のsshデバッグ情報

のssh -v [email protected]

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.xxx.com [192.168.xxx.xxx] port 22. 
debug1: Connection established. 
debug1: identity file /Users/abc/.ssh/id_rsa type -1 
debug1: identity file /Users/abc/.ssh/id_rsa-cert type -1 
debug1: identity file /Users/abc/.ssh/id_dsa type -1 
debug1: identity file /Users/abc/.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 d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60 
debug1: Host 'gitlab.corp.com' is known and matches the RSA host key. 
debug1: Found key in /Users/abc/.ssh/known_hosts:127 
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,password,hostbased 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn0 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn6 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn1 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn2 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn5 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn8 
Received disconnect from 192.168.100.218: 2: Too many authentication failures for git 
[email protected]:~/.ssh$ 
[email protected]:~/.ssh$ ls 
authorized_keys id_rsa   known_hosts  tmp/ 
[email protected]:~/.ssh$ rm known_hosts 
[email protected]:~/.ssh$ ssh -v [email protected] 
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.corp.com [192.168.100.218] port 22. 
debug1: Connection established. 
debug1: identity file /Users/abc/.ssh/id_rsa type -1 
debug1: identity file /Users/abc/.ssh/id_rsa-cert type -1 
debug1: identity file /Users/abc/.ssh/id_dsa type -1 
debug1: identity file /Users/abc/.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 d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60 
The authenticity of host 'gitlab.corp.com (192.168.100.218)' can't be established. 
RSA key fingerprint is d7:11:d8:62:a6:30:1d:4a:c7:f1:99:bd:ba:54:de:60. 
Are you sure you want to continue connecting (yes/no)? yes 
Warning: Permanently added 'gitlab.corp.com,192.168.100.218' (RSA) to the list of known hosts. 
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,password,hostbased 
debug1: Next authentication method: publickey 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn0 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn6 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn1 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn2 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn5 
debug1: Authentications that can continue: publickey,password,hostbased 
debug1: Offering RSA public key: /Users/abc/.ssh/id_rsa.cn8 
Received disconnect from 192.168.100.218: 2: Too many authentication failures for git 
+0

intellijは%HOME%\ sshと同じキーを使用していませんか?試してみてくださいhttp://stackoverflow.com/a/26427400/6309 – VonC

+0

@VonCありがとう、私は私のrsa証明書を再作成したくないのです。なぜなら、私のプロダクションサーバのログインssh検証 – Alexis

+0

異なる名前で、必要な数のキーを作成できます。 – VonC

答えて

5

あなたは、必要な右の公開鍵/秘密鍵を参照するために、別のssh urlを使用することができます。
configという名前で、あなたのHOME /の.sshファイルに追加します。

Host   mygitlab 
Hostname  gitlab.xxx.com 
User   git 
IdentityFile ~/.ssh/id_rsa.gitlab 
IdentitiesOnly yes 

そして、あなたのURLを変更します。

git clone mygitlab:xxx/myproj.git myproj 

そのように、あなたがしようとするsshのためにすべてのキーを提示し、デフォルトのSSHの動作を回避。

3

まず第一に、あなたのSSHキーを設定します。私たちのキーが正しく設定されている場合は

- あなたは、プロセスのPIDを確認する必要があり、あなたはキーがロードされますrはssh-agentのに

eval $(ssh-agent) 

を再起動してみてください。

鍵を手動で追加するには、ssh-addを使用します。これにより、あなたからの鍵がロードされます.sshフォルダ

+0

ssh-addは私が逃した重要なステップでした。ありがとうございました –

0

は最終的に - ホストマシンの原始的な再起動は

3

enter image description here

SourceTreeで、Open SSHPuTTY/PlinkからSSH Clientを変更してみてください...動作しますが、実際に何が起こるかを知っていただきたいと思います。

関連する問題