-
-
Notifications
You must be signed in to change notification settings - Fork 579
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fingerprint check failing for github #1998
Comments
Yes, it changed in late March. |
Will this be reflected in an updated Flatpak? |
Bitbucket.org also rotated their keys recently. I was able to update the fingerprint to the new one on my Mac using the script in this answer: https://superuser.com/questions/1088165/get-ssh-key-fingerprint-in-old-hex-format-on-new-version-of-openssh/1254573#1254573. One note on the Mac you need to use |
Fixed by 6cfd602 |
You can find session logs by date and version information in:
~/.config/org.sparkleshare.SparkleShare/logs/ on Linux and macOS
C:\Users\YOUR_USERNAME\AppData\Roaming\org.sparkleshare.SparkleShare\logs\ on Windows
To help us help you, please include the logs from around the time the issue occurred, as well as the SparkleShare version and info about your OS (displayed at the top of the log files). Then, tell us roughly in these steps what went wrong:
What happened:
I tried to set up sparkleshare with github
What I expected to happen:
I expected sparkleshare to connect to github
This happens when:
I follow the steps on the wiki for setting up github
here are the logs for when it failed:
for some reason, the fingerprint I get from GitHub is:
b8:d8:95:ce:d9:2c:0a:c0:e1:71:cd:2e:f5:ef:01:ba:34:17:55:4a:4a:64:80:d3:31:cc:c2:be:3d:ed:0f:6b
which is different than the fingerprint saved in the GitHub preset:
9d:38:5b:83:a9:17:52:92:56:1a:5e:c4:d4:81:8e:0a:ca:51:a2:64:f1:74:20:11:2e:f8:8a:c3:a1:39:49:8f
I was able to fix this by building locally after replacing the fingerprint in this file
Has GitHub changed its fingerprint? or is this just a problem with however I have my ssh hosts set up? is there an easier way to fix this without having to rebuild?
Thanks for reporting your issue or feature request, it helps lots!
The text was updated successfully, but these errors were encountered: