【问题标题】:public key denied, but ssh key accepted公钥被拒绝,但 ssh 密钥被接受
【发布时间】:2013-09-28 17:18:27
【问题描述】:

当我 git push 收到错误时,我无法推送到 git(或者更确切地说,git 对我有问题):

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

为此,我查看了 git 的 help page,但他们建议的所有“测试”都通过了,包括通过运行 $ ssh -vT git@github.com 检查是否使用了正确的密钥。根据我在 SO 上看到的帖子,这似乎是大多数人搁浅的地方,但它对我有用。这是我遗漏的情况下的输出。

OpenSSH_5.2p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to github.com [192.30.252.130] port 22.
debug1: Connection established.
debug1: identity file /Users/charliekim/.ssh/identity type -1
debug1: identity file /Users/charliekim/.ssh/id_rsa type 1
debug1: identity file /Users/charliekim/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debian-5ubuntu1+github5
debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1+github5 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 'github.com' is known and matches the RSA host key.
debug1: Found key in /Users/charliekim/.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: /Users/charliekim/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
PTY allocation request failed on channel 0
Hi **! 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 2496, received 3048 bytes, in 0.3 seconds
Bytes per second: sent 9462.3, received 11554.9
debug1: Exit status 1

这是.git/config中的远程URL

[remote "origin"]
    url = ssh://github.com/[user]/[repo].git
    fetch = +refs/heads/*:refs/remotes/origin/*

【问题讨论】:

  • 你能告诉我们你的遥控器在.git/config的网址吗?
  • 完成并完成,请参阅更新。谢谢!

标签: git github ssh


【解决方案1】:

您的 git 配置缺少用户,因此 git 尝试以您 (charliekim) 的身份进行身份验证,而不是作为 Github 期望的用户 git

使用正确的用户,你应该可以连接:

[remote "origin"]
    url = ssh://git@github.com/[user]/[repo].git
    fetch = +refs/heads/*:refs/remotes/origin/*

【讨论】:

  • @ThomasOrozco:作为一般提示:从 Github 上的 repo 页面复制 repo URL。这将为您节省这样的问题,以及一些相关的问题(例如,Github 上的 repo URL 目前区分大小写)——如果 Github 已经为您提供了完整的 URL,为什么还要麻烦手动输入它;)
  • @NevikRehnel 是的,这是正确的(如果您创建了 repo,Github 甚至会为您提供实际的 CLI):)
  • eep——我之前的评论是针对@dax heh。 名字太混乱了
猜你喜欢
  • 2020-02-11
  • 1970-01-01
  • 2021-01-21
  • 1970-01-01
  • 2018-04-12
  • 2019-11-24
  • 2014-11-08
  • 2019-03-11
  • 1970-01-01
相关资源
最近更新 更多