Menu
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.
902
Check your spelling If you try to clone [email protected]:user/repo. git , but the repository is really named User/Repo you will receive this error. To avoid this error, when cloning, always copy and paste the clone URL from the repository's page.
SSH Key pairs in general do not have an expiration date because they do not have metadata outside of their key strings.
If you need to clone a private GitHub repository without an SSH key you can use a Personal Access Token. This can be useful in a build/deployment pipeline for example where you are using a programmatic GitHub user to clone into a temporary server or container.
This seems to be a recent issue around Fedora 33. This is the relevant bug report.
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 [email protected] and grep the output for debug1: send_pubkey_test: no mutual signature algorithm.
The current workaround, as listed in the bug report, is to explicitly specify ssh-rsa support in your ~/.ssh/config:
Add the following entry to your ~/.ssh/config and make sure it has the permission chmod 700 ~/.ssh/config
Host bitbucket.org
User git
PubkeyAcceptedKeyTypes ssh-rsa
Replace bitbucket.org with whatever git host you are using
62
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With