Git权限被拒绝（公钥）

Question

我已经创建了连接到网络驱动器的SSH密钥。唯一的问题是，当网络驱动器无法访问时，我的Git pull/push将由于找不到SSH密钥而无法使用。因此，我决定在Windows驱动器上添加新的密钥。 我已经添加了新的SSH密钥，但是在拉取/推送代码时收到了以下错误：

Permission denied (publickey).
fatal: Could not read from remote repository.

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

我运行以下命令：

1) $ eval `ssh-agent` 
2) ssh-add /d/ssh/id_rsa

在那之后，我能够进行拉取/推送。但是每当我重新启动计算机时，都需要运行这两个命令才能解决问题。每次运行命令并不是一个好的解决方案。那么有没有好的解决方案，可以避免运行命令呢。

注意：我已经从网络驱动器中删除了所有先前的ssh密钥。

更新：

运行ssh -vvv bitbucket.org命令后，输出如下。

OpenSSH_7.1p2, OpenSSL 1.0.2h  3 May 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to bitbucket.org [104.192.143.1] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /z/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4
debug1: match: OpenSSH_6.4 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bitbucket.org:22 as 'Azam.Alvi'
debug3: hostkeys_foreach: reading file "/z/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /z/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: order_hostkeyalgs: prefer hostkeyalgs: [e-mail],ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: [e-mail],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: [e-mail],ssh-rsa,[e-mail],[e-mail],[e-mail],[e-mail],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: kex_parse_kexinit: [e-mail],aes128-ctr,aes192-ctr,aes256-ctr,[e-mail],[e-mail],arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[e-mail]
debug2: kex_parse_kexinit: [e-mail],aes128-ctr,aes192-ctr,aes256-ctr,[e-mail],[e-mail],arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[e-mail]
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-sha1,[e-mail],[e-mail],[e-mail],[e-mail],hmac-md5,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-sha1,[e-mail],[e-mail],[e-mail],[e-mail],hmac-md5,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[e-mail],zlib
debug2: kex_parse_kexinit: none,[e-mail],zlib
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: first_kex_follows 0
debug2: 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-dss,ssh-rsa
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[e-mail],[e-mail],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[e-mail]
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,[e-mail],[e-mail],aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,[e-mail]
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-md5,hmac-sha1,[e-mail],[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: [e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],[e-mail],hmac-md5,hmac-sha1,[e-mail],[e-mail],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[e-mail],hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,[e-mail]
debug2: kex_parse_kexinit: none,[e-mail]
debug2: kex_parse_kexinit:
debug2: kex_parse_kexinit:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: server->client aes128-ctr [e-mail] none
debug1: kex: client->server aes128-ctr [e-mail] none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaYXaGp1A
debug3: hostkeys_foreach: reading file "/z/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /z/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from bitbucket.org
debug3: hostkeys_foreach: reading file "/z/.ssh/known_hosts"
debug3: record_hostkey: found key type RSA in file /z/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 104.192.143.1
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /z/.ssh/known_hosts:1
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: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /d/ssh/id_rsa (0x600072470),
debug2: key: /z/.ssh/id_rsa (0x0),
debug2: key: /z/.ssh/id_dsa (0x0),
debug2: key: /z/.ssh/id_ecdsa (0x0),
debug2: key: /z/.ssh/id_ed25519 (0x0),
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
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: /d/ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
debug1: Authentications that can continue: publickey
debug1: Trying private key: /z/.ssh/id_rsa
debug3: no such identity: /z/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /z/.ssh/id_dsa
debug3: no such identity: /z/.ssh/id_dsa: No such file or directory
debug1: Trying private key: /z/.ssh/id_ecdsa
debug3: no such identity: /z/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: /z/.ssh/id_ed25519
debug3: no such identity: /z/.ssh/id_ed25519: No such file or directory
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

- Azam Alvi

Answer 1

创建 ssh_config 文件：

Host git_hostname # probably bitbucket.org
  IdentityFile /d/ssh/id_rsa

配置文件应该在~/.ssh/config中。当运行ssh -vvv bitbucket.org时，您应该能够找到客户端正在读取的配置。

- Jakuje

---

我正在使用Windows，那么我应该在哪里创建这个文件？ - Azam Alvi

当运行ssh -vvv bitbucket.org时，您应该能够找出客户端正在读取哪个配置。 - Jakuje

当我尝试使用ssh -vvv查找时，大多数情况下我发现的是/z/.ssh/*路径，这是一个网络路径，但现在它已经不存在了。 - Azam Alvi

使用上述命令更新问题并包含完整日志。 - Jakuje

请使用全局配置文件 /etc/ssh/ssh_config 或本地配置文件 /z/.ssh/config。 - Jakuje

Answer 2

当您在存储库中添加SSH支持时，也可能会出现此问题。可以通过以下步骤解决：

1. Goto SSH

   cd ~/.ssh
   

2. List existing Keys

   ls -al ~/.ssh
   

3. Use this command to create the SSH keys

   ssh-keygen -t rsa -C "[e-mail]"
   

4. Use this command to start your ssh-agent if it's not already running

   eval `ssh-agent`
   

5. Then add your private key file to SSH

   ssh-add ~/.ssh/<private_key_file>
   

6. Copy and paste your key in Bitbucket/ Github with

   cat ~/.ssh/<public_key_file> | pbcopy
   

7. Sometime it does not persists between reboot. Then you have to add below lines in .ssh/config (For Mac)

   Host *
       UseKeychain yes
       AddKeysToAgent yes
       IdentityFile ~/.ssh/<private_key_file>
   

8. In case if you want to use multiple Git accounts. Lets say you have to Github and Bitbucket both on a system. Then you need to create separate SSH keys for GitHub and Bitbucket and you mention both in the config file like below.

   Host *
       UseKeychain yes
       AddKeysToAgent yes
   
   #Bitbucket
       Host bitbucket.org
       User git
       IdentityFile ~/.ssh/bb-ssh-key
   
   #GitHub
       Host github.com
       User git
       IdentityFile ~/.ssh/github-ssh-key
   

- Shahbaz Hashmi