Git权限被拒绝（公钥）

Question

我已经为我的网络驱动器创建了 ssh 密钥。唯一的问题是，当网络驱动器无法访问时，由于找不到 ssh 密钥，我的 git pull/push 无法正常工作。所以我决定在我的 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

之后我可以拉/推。但是，每当我重新启动计算机时，我需要运行这 2 个命令时再次出现问题。这不是每次都运行的好解决方案。那么有什么好的解决方案让我不需要运行命令。

注意：我已经从我的网络驱动器中删除了所有以前的 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: ssh-rsa-cert-v01@openssh.com,ssh-rsa
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
debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-rsa,ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,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: 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,aes128-gcm@openssh.com,aes256-gcm@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,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: first_kex_follows 0
debug2: reserved 0
debug1: kex: server->client aes128-ctr umac-64-etm@openssh.com none
debug1: kex: client->server aes128-ctr umac-64-etm@openssh.com 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).

Answer 1

用

创建ssh_config

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

它应该在~/.ssh/config。在运行ssh -vvv bitbucket.org 时，您应该能够找出您的客户端正在读取什么配置。

Answer 2

当您在存储库中添加 SSH 支持时也会发生这种情况。并且可以通过以下步骤修复：

1. 转到 SSH

   cd ~/.ssh
   

2. 列出现有密钥

   ls -al ~/.ssh
   

3. 使用此命令创建 SSH 密钥

   ssh-keygen -t rsa -C "your_email@example.com"
   

4. 如果 ssh-agent 尚未运行，请使用此命令启动它

   eval `ssh-agent`
   

5. 然后将你的私钥文件添加到 SSH

   ssh-add ~/.ssh/<private_key_file>
   

6. 将您的密钥复制并粘贴到 Bitbucket/Github 中

   cat ~/.ssh/<public_key_file> | pbcopy
   

7. 有时它不会在重新启动之间持续存在。然后你必须在 .ssh/config (Mac) 中添加以下行

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

8. 如果您想使用多个 Git 帐户。假设您必须在系统上同时使用 Github 和 Bitbucket。然后，您需要为 GitHub 和 Bitbucket 创建单独的 SSH 密钥，并在下面的配置文件中提到这两者。

   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