MacOS下git clone git@github.com: Permission denied （publickey）錯誤及解決方式

最新推荐文章于 2024-09-26 14:23:13 发布
最新推荐文章于 2024-09-26 14:23:13 发布
阅读量3.9k 收藏 1
点赞数 1
分类专栏： macOS 文章标签： git MacOS

MacOS下git clone git@github.com: Permission denied （publickey）錯誤及解決方式

前言

這個錯誤是筆者在使用以下指令時發生的：

git clone git@github.com:dcos/dcos-cli.git

錯誤訊息

Cloning into ‘dcos-cli’…
Warning: Permanently added the RSA host key for IP address ‘192.30.253.113’ to the list of known hosts.
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

解決辦法

GitHub Help - Error: Permission denied (publickey)中有給出完整的問題排除方法。
以下記錄筆者實測的結果。

改用git當使用者名稱

如果原先使用的是：

ssh -T GITHUB-USERNAME@github.com

請將使用者名稱改為git：

ssh -T git@github.com

但在筆者的機器上還是輸出：

git@github.com: Permission denied (publickey).

所以問題不在這裡。

檢查是否有使用key

在背景啟動ssh-agent：

eval "$(ssh-agent -s)"

Agent pid 67142

檢查是否有私鑰且己載入ssh：

ssh-add -l -E md5

The agent has no identities.

如果輸出不是像：

2048 MD5:a0:dd:42:3c:5a:9d:e4:2a:21:52:4e:78:07:6e:c8:4d /Users/you/.ssh/id_rsa (RSA)

則需要生成新的ssh key並將它與GitHub關聯。
下面這個部份來自：GitHub Help - Generating a new SSH key and adding it to the ssh-agent。

生成新的ssh key

ssh-keygen -t rsa -b 4096 -C "your_email@example.com"

如果過程中出現Enter file in which to save the key，可以直接按Enter略過，使用預設的檔案路徑。
如果出現Enter passphrase，可以輸入自己的密碼或直接按Enter略過。
輸出：

Generating public/private rsa key pair.
Enter file in which to save the key (/Users/yourname/.ssh/id_rsa): 
/Users/yourname/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /Users/yourname/.ssh/id_rsa.
Your public key has been saved in /Users/yourname/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:CXtXJ/s8V00b5oz474OUm2lHsBrtP7fgU3eWYy4eCYs mimifasosofamire1123@gmail.com
The key's randomart image is:
+---[RSA 4096]----+
|                 |
|                 |
|      .     o .o.|
|       o . ..==.+|
|      . S .oo.+++|
|       . ...+B.*=|
|         E .==&.=|
|           ..X+B.|
|            oo*==|
+----[SHA256]-----+

經過這一步以後，新的key己經生成，被存在~/.ssh/config這個路徑下。
我們可以用cat來查看它的內容：

cat ~/.ssh/config

# --- Sourcetree Generated ---
Host yourgithubname-GitHub
	HostName github.com
	User yourgithubname
	PreferredAuthentications publickey
	IdentityFile /Users/yourname/.ssh/yourgithubname-GitHub
	UseKeychain yes
	AddKeysToAgent yes
# ----------------------------

ForwardX11 yes

因為這時key己經生成，這時候可以回去用ssh-add -l -E md5來查看key是否己載入ssh：

2048 MD5:03:57:c1:67:f1:04:20:7d:73:4b:91:d4:39:7d:90:47 /Users/yourname/.ssh/id_rsa (RSA)

可以發現己經有id了。

這時用ssh -vT git@github.com試著連接到git@github.com，來檢查剛剛生成的key是否己被使用：

OpenSSH_7.6p1, LibreSSL 2.6.2
debug1: Reading configuration data /Users/yourname/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: /etc/ssh/ssh_config line 52: Applying options for *
debug1: Connecting to github.com port 22.
debug1: Connection established.
debug1: identity file /Users/yourname/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6
debug1: Remote protocol version 2.0, remote software version babeld-f43b814b
debug1: no match: babeld-f43b814b
debug1: Authenticating to github.com:22 as ‘git’
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host ‘github.com’ is known and matches the RSA host key.
debug1: Found key in /Users/yourname/.ssh/known_hosts:4
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:FbFoShO5TA4eD6fXyLjyJJbPGvO8CGO00ZXMmR/7H8I /Users/yourname/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering public key: RSA SHA256:CXtXJ/s8V00b5oz474OUm2lHsBrtP7fgU3eWYy4eCYs /Users/yourname/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Trying private key: /Users/yourname/.ssh/id_dsa
debug1: Trying private key: /Users/yourname/.ssh/id_ecdsa
debug1: Trying private key: /Users/yourname/.ssh/id_ed25519
debug1: No more authentication methods to try.
git@github.com: Permission denied (publickey).

結果仍然是Permission denied。
這是因為我們尚未將ssh key添加到ssh-agent及GitHub帳戶所致。

將ssh key添加到ssh-agent

在背景啟動ssh-agent：

eval "$(ssh-agent -s)"

將ssh私鑰加入ssh-agent：

ssh-add -K ~/.ssh/id_rsa

這一步完成後，還需將ssh key加入GitHub帳戶。

將SSH key加入GitHub帳戶

此處內容來自：GitHub Help - Adding a new SSH key to your GitHub account。

將~/.ssh/id_rsa.pub檔案裡的內容複製到剪貼簿：

pbcopy < ~/.ssh/id_rsa.pub

前往GitHub頁面，找到右上角的+號→SSH and GPG keys→New SSH key或Add SSH key。

這時會出現兩個欄位：
在Title欄位輸入有意義的名稱，如iMac，Personal MacBook Air。
在Key欄位貼上剛剛複製的內容。
最後點擊Add SSH key來完成ssh key的添加。

檢查ssh key是否有被使用

可以再次使用以下指令，來檢查剛添加的key有沒有被使用：

ssh -vT git@github.com

OpenSSH_7.6p1, LibreSSL 2.6.2
debug1: Reading configuration data /Users/yourname/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 48: Applying options for *
debug1: /etc/ssh/ssh_config line 52: Applying options for *
debug1: Connecting to github.com port 22.
debug1: Connection established.
debug1: identity file /Users/yourname/.ssh/id_rsa type 0
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /Users/yourname/.ssh/id_ed25519-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_7.6
debug1: Remote protocol version 2.0, remote software version babeld-f43b814b
debug1: no match: babeld-f43b814b
debug1: Authenticating to github.com:22 as ‘git’
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host ‘github.com’ is known and matches the RSA host key.
debug1: Found key in /Users/yourname/.ssh/known_hosts:4
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering public key: RSA SHA256:FbFoShO5TA4eD6fXyLjyJJbPGvO8CGO00ZXMmR/7H8I /Users/yourname/.ssh/id_rsa
debug1: Authentications that can continue: publickey
debug1: Offering public key: RSA SHA256:CXtXJ/s8V00b5oz474OUm2lHsBrtP7fgU3eWYy4eCYs /Users/yourname/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 535
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.253.112]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: network
debug1: Sending environment.
debug1: Sending env LANG = de_DE.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi yourgithubname! You’ve successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3760, received 2060 bytes, in 0.8 seconds
Bytes per second: sent 4446.1, received 2435.9
debug1: Exit status 1

這時再次使用：

git clone git@github.com:dcos/dcos-cli.git

發現它己經能正常運作了！

參考連結

GitHub Help - Error: Permission denied (publickey)
GitHub Help - Generating a new SSH key and adding it to the ssh-agent
GitHub Help - Adding a new SSH key to your GitHub account

keineahnung2345
关注
专栏目录
macOS github 如何解决SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
iCloudEnd的博客
08-04 1082
最新我在研究flutter desktop开发，但是运行flutter upgrade总是提示下面的问题 解决方案 我在使用时遇到了类似的错误wget …，在 Internet 上进行了多次无果的搜索后，我发现它是在将主机名解析为 IPv6 地址时发生的。我通过比较两台机器的输出发现了这一点wget …，一台正在解析为 IPv4，它在那里工作，另一台正在解析为 IPv6，但在那里失败了。所以我的解决方案是 在 macOS 上运行。...
Mac 系统 vscode 上传 github 问题 LibreSSL SSL_connect: Operation timed out in connection to github.com:443
AItrust的博客
12-24 3033
问题 更改了 SSH 的 key 后，使用 vscode 上传 git 出现报错 fatal: unable to access 'https://github.com/Ryan906k9/SpotmicroaiT/': LibreSSL SSL_connect: Operation timed out in connection to github.com:443 解决方法 首先，删除本机项目文件夹下面的 .git 文件夹 然后打开终端，进入项目所在目录 git init 重新初始化了 .git 文
macos使用github提示git@github.com: Permission denied (publickey)
Mint6的博客
01-17 919
生成新 SSH 密钥并添加到 ssh-agent - GitHub Docs
mac：出现Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). fatal: Could not read fro
鄙人kunzhi96，感恩遇见！
04-19 3822
升级macOS后出现的问题。需要输入密码，之前没有输入过密码，输入三次密码还报错 报错：Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). fatal: Could not read from remote repository. Please make sure you have the correct access rights 需要在 .ssh/config 增加一些配置才行。
【git】git报错：Permission denied (publickey) 解决办法
最新发布
lemonxiaoxiao的博客
09-26 1191
3、 登录对应的git服务器、将公钥（id_rsa.pub中的内容）添加上去。2、 找到生成Key值的目录,前往.ssh目录、查看对应的公钥。注意：内容是（以ssh-rsa 开头，以账号的注册邮箱结尾的）完成之后、输入以下命令、查看是否OK、出现如下内容表示成功。再次进行克隆、如果出现如下、则表示克隆成功。注意：输入的是自己的邮箱地址。1、 生成SSH key。
Mac os 13更新，Git报 Permission denied (publickey).
Trinity_Yin的博客
12-19 1699
Permission denied (publickey).解决方案
MAC电脑gitt@github.com: Permission denied (publickey). fatal: Could not read from remote repository
weixin_44468956的博客
06-15 1634
gitt@github.com: Permission denied (publickey). fatal: Could not read from remote repository
git@github.com: Permission denied (publickey) issue for Mac
XUANEER的博客
04-26 539
首先用 ssh -vT git@github.com 测试一下，会去你用户目录下面找公钥文件, 有打印出下面的信息,这说明/User/用户名/.ssh/ 下面去寻找公钥文件，当前用户目录下面的确没有公钥文件 debug1: No more authentication methods to try. git@github.com: Permission denied (publickey). 执行: cd /Users/xxx/.ssh/ 执行: ssh-keygen -t rsa -b 4096 .
git@github.com: Permission denied (publickey).
msatergz的博客
06-23 246
我再Mac上用git可以正常push和clone，但是再windows上就提示git@github.com: Permission denied (publickey). 后来，在博客园https://www.cnblogs.com/wmr95/p/7852832.html这篇博客的指导下，成功解决问题，在这里就记录一下。 首先 在git bash键入 ssh -v git@github.com ...
Permission denied (publickey). fatal: Could not read from remote repository.
weixin_30325971的博客
11-17 570
　　博主在github上下载tiny face的的源代码的时候，遇到git clone命令为：git clone --recursive git@github.com:peiyunh/tiny.git 　　而当我在ternimal下执行这条语句的时候，出现错误： 　　Permissiondenied (publickey). 　　fatal:Could not read from remot...
gitextensions.github.io:网站
05-08
Git Extensions 是一个强大的开源工具，它提供了一个图形用户界面（GUI）来管理和操作Git版本控制系统。这个工具使得非命令行用户也能轻松地进行版本控制操作，如提交、推送、拉取、合并等。Git Extensions 不仅支持...
estherjk.github.io:我的个人网站的源代码-git source code
03-25
在macOS上，通过 brew install rbenv ： brew install rbenv 安装： gem install bundler 将gems安装到项目根目录中的隐藏文件夹中： bundle install --path=.gems 本地服务器设置 运行服务器 ./.scripts/start-...
Mac npm install时提示git@github.com:Permission denied (publickey)
wejack的专栏
01-25 2036
Mac npm install时提示git@github.com:Permission denied (publickey)
连接GitHub报错git@github.com: Permission denied (publickey)解决方法
Parzival_的博客
01-12 857
解决方法：重新添加私钥 ssh-add -K ~/.ssh/id_rsa_github
Mac系统 Git远程克隆仓库出现Permission denied (publickey) 如何生成私钥、公钥
weixin_42828741的博客
10-02 4343
由于电脑重装再次会想起首次配置git远程克隆仓库的bug，出现以下bug The authenticity of host 'gitee.com (手动打码)' can't be established. ECDSA key fingerprint is 手动打码. Are you sure you want to continue connecting (yes/no)? y Please ty...
【git】git@github.com: Permission denied (publickey).报错问题
热门推荐
woyizhizaizhaoni的专栏
12-03 1万+
git多账号连接报错问题
解决Git@github.com: Permission denied (publickey).的问题指导
t13237652134的博客
09-24 1528
步骤四： 登录GitHub平台，点击右上角个人中心后，下拉点击setting，切换SSH 按到 GPG Keys ，再点击new SSh key ，输入title + 复制的公钥（粘贴时注意把最后的空格去掉）1. 背景使用Pycharm 工具对 github平台上的代码clone下来时，提示权限被拒绝（Permission denied ），导致无法clone和pull最新的代码。：直接敲三次回车键后，即可在本地生成密钥、公钥 (生成如下样式即可)==> 输入你github平台绑定的邮箱地址。
MAC SSH：XXX@IP:Permission denied(publickey)
技术，就是不断的深入～
10-28 980
注意：这个问题的根本原因是由于OPENSSH的版本导致的，macOS ventura系统默认使用的版本为9.x，而本地的ssh密钥一般是rsa格式的，而9.x的版本对于rsa的支持默认是关闭的。保存文件之后，再次执行，ssh命令就不会有这个问题。之后会对这个过程进行详细列举。
Mac电脑github提示：Permission denied (publickey). fatal: Could not read from remote repository.
jiva123的博客
02-01 9344
Permission denied (publickey). fatal: Could not read from remote repository. 　　在github上下载jivaklong/Real-Time-Voice-Cloning的的源代码的时候，遇到git clone命令为：git clone git@github.com:jivaklong/Real-Time-Voice-Cloning.git 执行苹果终端ternimal下执行这条语句的时候，出现错误： 　　Permissionden
git@62.234.13.38's password: Permission denied, please try again.
09-01
当你在使用 git 命令时，如果出现 "Permission denied" 的错误提示，通常是由于没有正确的身份验证导致的。首先，确保你已经在 GitHub 账户中设置了 SSH 密钥，这样你才能通过 SSH 协议进行身份验证。 另外，如果你在 macOS Mojave 中执行 `brew update` 命令时遇到了 "Permission denied" 的错误提示，可能是由于文件权限问题导致的。你可以尝试使用 `sudo` 命令以管理员身份运行该命令，或者检查你的文件和目录权限是否正确设置。你可以参考这篇文章来解决该问题。 同时，当你在执行 git 命令时出现 "Permission denied" 的错误提示，并且显示 "git@62.234.13.38's password" 时，这通常意味着你需要提供正确的密码才能进行身份验证。请确保你输入的密码是正确的，并且你具有相应的权限来访问该资源。如果问题仍然存在，请检查你的网络连接是否正常，或者联系服务器管理员以获取更多帮助。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* [npm安装vue-element-admin时遇到git.EXE ls-remote -h -t ssh://git@github.com错误error code: 128](https://blog.csdn.net/qq_27361945/article/details/123739009)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] - *2* *3* [自己建仓库并同步部署到宝塔，后期报错：Unable to create /path /.git/index.lock : Permission denied](https://blog.csdn.net/kfgauss/article/details/109639226)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatsearchT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值