Ubuntu Github的ssh键问题

前端之家收集整理的这篇文章主要介绍了Ubuntu Github的ssh键问题前端之家小编觉得挺不错的,现在分享给大家,也给大家做个参考。
我遵循本指南中的每一步:
http://help.github.com/linux-key-setup/

当我到最后,我可以ssh到git@github.com,得到的回应:

PTY allocation request Failed on channel 0
Hi AlexBaranosky! You’ve successfully authenticated,but GitHub does not provide shell access.
Connection to github.com closed

但是当我去克隆我的repo它不会说:

Permission denied (publickey).
fatal: The remote end hung up unexpectedly

我使用过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
您是否以root身份运行Github指南中的所有命令?鉴于您已经注意到了解决方案,这是目前唯一可以想象的情况.

在任何方面作为根本,是非常危险的,如果可能的话应该避免.

我强烈建议您重新运行这些说明,作为您自己的用户.我第二次Ray的建议再次尝试用-v,我们可以帮助你.使用root,特别是对于这个开发推送过程,是危险的.所有这一切都是为了删除树(rm -rf tree *),并且意外地在树和*,bam之间添加空格,丢失了大量的内容.你也可以做得更糟.

猜你在找的Ubuntu相关文章