Git ssh要求输入密码,即使我已生成密钥

Git ssh要求输入密码,即使我已生成密钥,git,ssh,passwords,key,opensuse,Git,Ssh,Passwords,Key,Opensuse,我在公司的gitlab服务器上使用一些git存储库。今天,我在我的机器上安装了opensuse,当我试图通过ssh克隆repos时,gitlab不断向我询问一个我没有的密码。在opensuse之前,我有ubuntu,一切都很好 我已经生成了我的密钥,并将我的公共密钥更新到我无权访问的gitlab服务器 我尝试使用我的gitlab密码,但什么也没有得到,只有: 权限被拒绝,请重试 在第三次尝试中,我得到: 权限被拒绝公钥、密码。致命:无法从中读取 远程存储库 请确保您拥有正确的访问权限和存储库 存

我在公司的gitlab服务器上使用一些git存储库。今天,我在我的机器上安装了opensuse,当我试图通过ssh克隆repos时,gitlab不断向我询问一个我没有的密码。在opensuse之前,我有ubuntu,一切都很好

我已经生成了我的密钥,并将我的公共密钥更新到我无权访问的gitlab服务器

我尝试使用我的gitlab密码,但什么也没有得到,只有:

权限被拒绝,请重试

在第三次尝试中,我得到:

权限被拒绝公钥、密码。致命:无法从中读取 远程存储库

请确保您拥有正确的访问权限和存储库 存在

这是我的开放ssh版本:

OpenSSH_6.6.1p1、OpenSSL 1.0.1k-fips 2015年1月8日

我的suse版本:

openSUSE 13.2 Harlequin x86_64位

这是sshing gitlab的跟踪:

OpenSSH_6.6.1, OpenSSL 1.0.1k-fips 8 Jan 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to gitlab.enterprise.it [10.254.150.182] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/facundo/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/facundo/.ssh/id_rsa type 1
debug1: identity file /home/facundo/.ssh/id_rsa-cert type -1
debug1: identity file /home/facundo/.ssh/id_dsa type -1
debug1: identity file /home/facundo/.ssh/id_dsa-cert type -1
debug1: identity file /home/facundo/.ssh/id_ecdsa type -1
debug1: identity file /home/facundo/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/facundo/.ssh/id_ed25519 type -1
debug1: identity file /home/facundo/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH_6.6.1* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "gitlab.enterprise.it" from file "/home/facundo/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/facundo/.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: 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,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-ed25519-cert-v01@openssh.com,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-ed25519,ssh-rsa,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,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-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,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: 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,diffie-hellman-group1-sha1
debug2: kex_parse_kexinit: ssh-rsa,ssh-dss,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,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-gcm@openssh.com,aes256-gcm@openssh.com,chacha20-poly1305@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,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: setup hmac-md5-etm@openssh.com
debug1: kex: server->client aes128-ctr hmac-md5-etm@openssh.com none
debug2: mac_setup: setup hmac-md5-etm@openssh.com
debug1: kex: client->server aes128-ctr hmac-md5-etm@openssh.com none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ECDSA f3:57:5c:28:52:8c:de:0a:58:6e:34:be:bf:72:90:e4 [MD5]
debug3: load_hostkeys: loading entries for host "gitlab.enterprise.it" from file "/home/facundo/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/facundo/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: load_hostkeys: loading entries for host "10.254.150.182" from file "/home/facundo/.ssh/known_hosts"
debug3: load_hostkeys: found key type ECDSA in file /home/facundo/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'gitlab.enterprise.it' is known and matches the ECDSA host key.
debug1: Found key in /home/facundo/.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/facundo/.ssh/id_rsa (0x7f6873bd97a0),
debug2: key: /home/facundo/.ssh/id_dsa ((nil)),
debug2: key: /home/facundo/.ssh/id_ecdsa ((nil)),
debug2: key: /home/facundo/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred 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/facundo/.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/facundo/.ssh/id_dsa
debug3: no such identity: /home/facundo/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ecdsa
debug3: no such identity: /home/facundo/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ed25519
debug3: no such identity: /home/facundo/.ssh/id_ed25519: No such file or directory
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@gitlab.enterprise.it's password:
我在谷歌上搜索了很多,但是我没有找到解决问题的方法。你知道会发生什么吗

我更新了gitlab的ssh连接跟踪,因为有人告诉我,我正在尝试使用两个可能的密钥进行连接,现在应该只有一个RSA密钥

我尝试从bitbucket存储库中克隆,但成功了。我还成功地通过SSH连接到另一台计算机,因此我几乎可以肯定SSH不是这里的问题,对吗

另外,我将另一台计算机的ssh跟踪与可以连接到它的gitlab进行了比较,它们在最后几行中开始有所不同:

成功的计算机:

[...]
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/username/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug2: input_userauth_pk_ok: fp f4:73:b3:7d:49:0d:4d:2b:a3:42:32:6c:49:c7:cf:e9
debug3: sign_and_send_pubkey: RSA f4:73:b3:7d:49:0d:4d:2b:a3:42:32:6c:49:c7:cf:e9
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to gitlab.enterprise.it ([10.254.150.182]:22).
debug2: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
[...]
[...]
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred 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/facundo/.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/facundo/.ssh/id_dsa
debug3: no such identity: /home/facundo/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ecdsa
debug3: no such identity: /home/facundo/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ed25519
debug3: no such identity: /home/facundo/.ssh/id_ed25519: No such file or directory
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@gitlab.enterprise.it's password:
我的电脑:

[...]
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/username/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug2: input_userauth_pk_ok: fp f4:73:b3:7d:49:0d:4d:2b:a3:42:32:6c:49:c7:cf:e9
debug3: sign_and_send_pubkey: RSA f4:73:b3:7d:49:0d:4d:2b:a3:42:32:6c:49:c7:cf:e9
debug1: key_parse_private2: missing begin marker
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
Authenticated to gitlab.enterprise.it ([10.254.150.182]:22).
debug2: fd 5 setting O_NONBLOCK
debug1: channel 0: new [client-session]
[...]
[...]
debug1: Authentications that can continue: publickey,password
debug3: start over, passed a different list publickey,password
debug3: preferred 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/facundo/.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/facundo/.ssh/id_dsa
debug3: no such identity: /home/facundo/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ecdsa
debug3: no such identity: /home/facundo/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /home/facundo/.ssh/id_ed25519
debug3: no such identity: /home/facundo/.ssh/id_ed25519: No such file or directory
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@gitlab.enterprise.it's password:

谢谢大家的回复,不过问题是通过让gitlab的管理员重置服务器解决的,因为我不是唯一一个有这个问题的人。

最有可能的访问权限尝试chmod 600~/.ssh~/.ssh/*,或者您忘记了复制密钥。跟踪显示ssh向github提供了两个密钥,github也不接受他们中的任何一个。您认为它应该使用什么密钥向github进行身份验证?