Fedora 33 git pull或clone不再起作用和/或ssh密钥不再被识别 [英] Fedora 33 git pull or clone no longer working and/or ssh key no longer recognized

问题描述

我最近设置了Fedora 33，并正在迁移我的文件.我复制了ssh密钥，发现无法再从旧笔记本电脑上提取的bitbucket git存储库提取. ssh密钥完全相同，并且公共密钥已经在bitbucket帐户上.此外，权限设置为chmod 600.我仍然无法从仓库中撤出.

I recently set up Fedora 33 and was migrating over my files. I copied over my ssh keys and found that I could no longer pull from bitbucket git repos I was able to pull from on my old laptop. The ssh keys are exactly the same, and the public key is already on the bitbucket account. Additionally the permissions were set to chmod 600. I still can not pull from the repo.

推荐答案

这似乎是有关Fedora 33的最新问题.这是相关的

This seems to be a recent issue around Fedora 33. This is the relevant bug report.

问题是Fedora 33似乎删除了对SHA1的支持，我想bitbucket.org通过ssh将SHA1用于其git clone.您可以通过运行ssh -Tv [e-mail]和grep debug1: send_pubkey_test: no mutual signature algorithm的输出来验证这是否是相同的问题.

The issue is that it seems like Fedora 33 removed support for SHA1, and I guess bitbucket.org uses SHA1 for their git clone via ssh. You can verify if this is the same issue by running ssh -Tv [e-mail] and grep the output for debug1: send_pubkey_test: no mutual signature algorithm.

错误报告中列出的当前解决方法是在~/.ssh/config中明确指定ssh-rsa支持:

The current workaround, as listed in the bug report, is to explicitly specify ssh-rsa support in your ~/.ssh/config:

将以下条目添加到您的~/.ssh/config

Add the following entry to your ~/.ssh/config

Host bitbucket.org
    User git
    PubkeyAcceptedKeyTypes ssh-rsa

将bitbucket.org替换为您正在使用的git主机

Replace bitbucket.org with whatever git host you are using

这篇关于Fedora 33 git pull或clone不再起作用和/或ssh密钥不再被识别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！