当
$ git clone -v git@heroku.com:testabcde.git Cloning into testabcde...
Heroku返回
Permission denied (publickey).
fatal: The remote end hung up unexpectedly
当
$ heroku keys
返回
=== 1 key for ohho@gmail.com
ssh-rsa AAAAB3NzaC...lXLyj9YQ== ohho@gmail.com
现在
$ ssh -v git@heroku.com -T
OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to heroku.com [50.19.85.154] port 22.
debug1: Connection established.
debug1: identity file /Users/ohho/.ssh/identity type -1
debug1: identity file /Users/ohho/.ssh/id_rsa type 1
debug1: identity file /Users/ohho/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5pgsql1
debug1: match: OpenSSH_5.1p1 Debian-5pgsql1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.2
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: Host 'heroku.com' is known and matches the RSA host key.
debug1: Found key in /Users/ohho/.ssh/known_hosts:5
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/ohho/.ssh/identity
debug1: Offering public key: /Users/ohho/.ssh/id_rsa
debug1: Remote: Forced command: /home/git/bin/git_proxy ohho@gmail.com
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
debug1: Offering public key: /Users/ohho/.ssh/id_dsa
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).
如何修复Permission denied (publickey)错误？
UPDATE(文件权限信息(:
drwxr-xr-x 11 ohho staff 374 Sep 16 09:37 .
drwxr-xr-x+ 50 ohho staff 1700 Sep 15 10:34 ..
-rw------- 1 ohho staff 1743 Sep 16 09:37 github_rsa
-rw-r--r-- 1 ohho staff 390 Sep 16 09:37 github_rsa.pub
-rw-r--r-- 1 ohho staff 390 Sep 9 09:47 github_rsa.pub_bak-github
-rw------- 1 ohho staff 1743 Sep 9 09:47 github_rsa_bak-github
-rw------- 1 ohho staff 736 Dec 2 2010 id_dsa
-rw-r--r-- 1 ohho staff 606 Dec 2 2010 id_dsa.pub
-rw------- 1 ohho staff 1743 Jan 28 2011 id_rsa
-rw-r--r-- 1 ohho staff 399 Jan 28 2011 id_rsa.pub
-rw-r--r--@ 1 ohho staff 10752 Sep 16 11:47 known_hosts
我遇到了同样的问题，可以解决以下问题：
ssh-add ~/.ssh/id_rsa
(添加到heroku的公钥的私钥(
使用msysgit，检查bash会话中对.ssh目录的权限(它们应该是700(以及其中的文件(600(
查看问题261，看看其中一个变通方法是否有效，比如(如果其他一切都失败了(用cygwin的一个替换ssh.exe。
OP ohho提到SO问题"git clone failed for Heroku project"，建议加载Heroku密钥(当它的名称与默认的id_rsa不同时(：
ssh-add ~/.ssh/heroku_rsa
这是一个解决方案，尤其是如果您已经有了id_rsa私钥(用于heroku以外的其他目的(
我对此也有同样的问题。我有一个应用程序，然后创建另一个应用，相同的帐户。第一个应用程序仍然可以使用git，但不能在第二个应用程序中使用git做任何事情，甚至其他操作(如日志…(仍然可以！
这对我有效：-清除heroku当前密钥：
heroku keys:clear
在~/.ssh/或windowsC:\Users\.ssh中删除您当前的私钥
创建新的密钥对：
ssh密钥生成-t rsa-C"your.email@domain.com">
上传到heroku:
heroku密钥：添加
它会列出你当前拥有的密钥对，并要求你上传一个，输入数字
完成。