Github - 致命身份验证失败 - 但我仍然可以连接?

Posted

技术标签:

【中文标题】Github - 致命身份验证失败 - 但我仍然可以连接?【英文标题】:Github - Fatal Authentication Failed - Yet I can still connect? 【发布时间】:2013-10-21 11:59:53 【问题描述】:

我的 github 没有连接。我尝试了两台不同的计算机,但我得到了同样的错误,很明显我做错了什么。当我运行git push 时,系统会按预期提示我输入用户名/密码。输入它们,是的,我输入正确。然后它说:

fatal: Authentication failed

但是,当我输入 ssh -T git@github.com 时,它会提示我输入密码,输入密码后,它会欢迎我访问 github。我尝试再次添加 SSH 密钥,但它只是说这个 SSH 密钥已经在帐户上。有人让我知道我错过了什么吗?

当我尝试登录时它显示:

Password for http://(UserName)@www.github.com:

对吗?

更多信息:这里是 ssh-vT git@github.com 的输出:

$ ssh-add -l
Could not open a connection to your authentication agent.

_

$ ssh -vT git@github.com
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Connecting to github.com [192.30.252.129] port 22.
debug1: Connection established.
debug1: identity file /l/.ssh/identity type -1
debug1: identity file /l/.ssh/id_rsa type 1
debug1: identity file /l/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.9p1 Debia
n-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_4.6
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc 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 /l/.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: Trying private key: /l/.ssh/identity
debug1: Offering public key: /l/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 277
debug1: read PEM private key done: type RSA
debug1: Authentication succeeded (publickey).
debug1: channel 0: new [client-session]
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.
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi ____! You've successfully authenticated, but GitHub does not provide shell ac
cess.
debug1: channel 0: free: client-session, nchannels 1
debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.1 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0
debug1: Exit status 1

【问题讨论】:

【参考方案1】:

如果你有这个问题,你基本上有两种解决方案可供选择:

    如果您坚持使用 HTTPS 连接到 Github,则需要从您在 Github 上的帐户获取个人访问令牌,而不是密码。 您需要切换到 SSH 并使用它来登录。

对于这两个选项,请查看 this Stack Overflow question and its excellent first answer 了解如何实施它们。

【讨论】:

【参考方案2】:

你可以试试……

1 编辑您的远程存储库

git remote set-url origin your-remote-repository-ssh-url

2 推送您的代码。

git push origin ...

你会在哪里找到你的 ssh-url?

1 在您的存储库页面中

2 点击 ssh 链接并复制你的 ssh-url

【讨论】:

【参考方案3】:

尝试通过ssh而不是通过http链接到github。做git remote set-url origin &lt;ssh url&gt; 然后尝试做git push

ssh url 应该类似于 git@github.com...

【讨论】:

以上是关于Github - 致命身份验证失败 - 但我仍然可以连接?的主要内容,如果未能解决你的问题,请参考以下文章

从 Visual Studio Code (1.62.2) 推送到 GitHub 时出现“致命:身份验证失败”

psql:致命:用户的 PAM 身份验证失败

无法 git push,致命:身份验证失败,用户名更改后

PostgreSQL - 致命:用户的身份验证失败

psql:致命:用户“postgres”的身份验证失败

Azure Devops OnPremise,致命:克隆 Git 存储库时身份验证失败