Question

我遵循了本指南中给出的每一步： http://help.github.com/linux-key-setup/

当我结束时，我可以ssh到git@github.com，得到回复：

通道0上的
PTY分配请求失败你好AlexBaranosky！您已成功通过身份验证，但GitHub不提供shell访问权限。与github.com的连接已关闭

但是当我去克隆我的回购时，它没有说：

权限被拒绝（publickey）。致命：远程端意外挂断

我经常使用Github，但这是我第一次使用Ubuntu计算机，我在这里缺少什么？

非常感谢任何帮助。

亚历

编辑：

ssh -v git@github.com

的内容

alex@ubuntu:~/proj$ ssh -v git@github.com
OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to github.com [207.97.227.239] port 22.
debug1: Connection established.
debug1: identity file /home/alex/.ssh/identity type -1
debug1: identity file /home/alex/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/alex/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1p1 Debian-5github2
debug1: match: OpenSSH_5.1p1 Debian-5github2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu4
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 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/alex/.ssh/known_hosts:1
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: Offering public key: /home/alex/.ssh/id_rsa
debug1: Remote: Forced command: gerve AlexBaranosky
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: Remote: Forced command: gerve AlexBaranosky
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.utf8
PTY allocation request failed on channel 0
Hi AlexBaranosky! You've successfully authenticated, but GitHub does not provide shell access.
              debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
Connection to github.com closed.
Transferred: sent 2592, received 2904 bytes, in 0.1 seconds
Bytes per second: sent 44942.9, received 50352.7
debug1: Exit status 1

正在投放的输出：git clone git@github.com:AlexBaranosky/Sportello.git

fatal: could not create work tree dir 'Sportello'.: Permission denied

Answer 1

您是否以root身份运行Github指南中的所有命令？鉴于您已经注意到的解决方案，这是我目前唯一能想象的方案。

在任何方面，以root身份工作都是非常危险的，如果可能的话应该避免。

我强烈建议您将这些说明作为自己的用户重新运行。我第二次使用-v再次尝试使用Ray的建议，我们可以从那一点帮助你。完全使用root，尤其是这个开发+推送过程，只是危险的。只需要删除一棵树（rm -rf tree*）并意外地在树和*之间添加空格，bam，丢失大量内容。你也可以做得更糟。

Answer 2

ssh可能会尝试多个键，直到找到一个有效的键。（令人困惑但很强大）

在详细模式中：

ssh -v git@github.com

您将看到使用哪个密钥ssh进行身份验证。

然后您可以重新调整密钥或将正确的文件名添加到主机github.com的〜/ .ssh / config

干杯

雷

Answer 3

我在新配置的Ubuntu机器上，必须确保我的SSH密钥配置正确。 http://help.github.com/linux-set-up-git/

Ubuntu Github ssh密钥问题

3 个答案: