Ssh Can'；无法连接到github

我一直在学习这个教程

但是，在执行

ssh时git@github.com

我正在接受

通道0上的PTY分配请求失败

如果我这样做

sshgit@github.com-v

我明白了

OpenSSH_5.8p1 Debian-1ubuntu3, OpenSSL 0.9.8o 01 Jun 2010
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/hailwood/.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/hailwood/.ssh/id_rsa-cert type -1
debug1: identity file /home/hailwood/.ssh/id_dsa type -1
debug1: identity file /home/hailwood/.ssh/id_dsa-cert type -1
debug1: identity file /home/hailwood/.ssh/id_ecdsa type -1
debug1: identity file /home/hailwood/.ssh/id_ecdsa-cert 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.8p1 Debian-1ubuntu3
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: Server host key: RSA 16:27:ac:a5:76:28:2d:36:63:1b:56:4d:eb:df:a6:48
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/hailwood/.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: Roaming not allowed by server
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 RSA public key: /home/hailwood/.ssh/id_rsa
debug1: Remote: Forced command: gerve hailwood
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 279
debug1: Remote: Forced command: gerve hailwood
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([207.97.227.239]:22).
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_NZ.UTF-8
PTY allocation request failed on channel 0

OpenSSH_5.8p1 Debian-1ubuntu3，OpenSSL 0.9.8o 2010年6月1日
debug1:读取配置数据/etc/ssh/ssh\u config
debug1:将选项应用于*
debug1:连接到github.com[207.97.227.239]端口22。
debug1:已建立连接。
debug1:identity file/home/hailwood/.ssh/id\u rsa类型1
debug1:检查黑名单文件/usr/share/ssh/blacklist.RSA-2048
debug1:正在检查黑名单文件/etc/ssh/blacklist.RSA-2048
debug1:identity file/home/hailwood/.ssh/id\u rsa-cert type-1
debug1:identity file/home/hailwood/.ssh/id_dsa type-1
debug1:identity file/home/hailwood/.ssh/id_dsa-cert type-1
debug1:identity file/home/hailwood/.ssh/id_ecdsa type-1
debug1:identity file/home/hailwood/.ssh/id_ecdsa-cert type-1
debug1：远程协议版本2.0，远程软件版本OpenSSH_5.1p1 Debian-5github2
debug1:match:OpenSSH_5.1p1 Debian-5github2 pat OpenSSH*
debug1:启用协议2.0的兼容模式
debug1:本地版本字符串SSH-2.0-OpenSSH_5.8p1 Debian-1ubuntu3
debug1:SSH2\u MSG\u KEXINIT已发送
debug1:SSH2\u MSG\u KEXINIT已收到
debug1:kex:server->client aes128 ctr hmac-md5无
debug1:kex:客户端->服务器aes128 ctr hmac-md5无
debug1:SSH2_MSG_KEX_DH_GEX_请求（1024Github不提供shell访问，因此尝试
ssh
到Github将失败（如您所见，身份验证成功，但您没有获得伪终端）。尝试
git clone
一些公共repo，看看它是否有效。
git提供shell访问，但在您进一步操作之后。请遵循他们提供的本教程：
实际上对于SSH，我建议这是不对的。当您尝试
SSH时git@github.com-v
，预期答案将以“
Hi USERNAME！您已成功通过身份验证，但GitHub不提供shell访问权限
“。OP没有得到那个答案，所以似乎他的SSH配置确实有问题。@RSENA:除了那个消息，日志输出与我得到的类似，包括上次PTY拒绝，所以我认为OP的SSH客户端没有显示来自服务器的最终消息（或者他忘了粘贴它）。由于OP接受了答案，我认为他成功地克隆了存储库；因此他的SSH设置可能是正确的。好的，很公平。无论如何，我想我的评论对其他有类似问题的人很重要，所以我会保留它。