[sr #110545] SSH key not recognized on Git commit

Update of sr #110545 (project administration): Assigned to:None => rwp Open/Closed:Open => Closed ___ Follow-up Comment #17: I think

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #16, sr #110545 (project administration): It was actually on the 24th that I switched the git services from the old server over to the new server. And there were some problems with incomplete setup found. I think we are past those problems. Past them unless and until someone

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #15, sr #110545 (project administration): Thank you, Bob! Much appreciated. Bests Luis ___ Reply to this item at: ___

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #14, sr #110545 (project administration): I have updated the wiki page with updated information concerning this issue. https://savannah.gnu.org/maintenance/SshAccess/ ___ Reply to this item at:

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #13, sr #110545 (project administration): [comment #12 comment #12:] > Just in case this help other, this issue manifests for me as a "Host key verification failed" Noting that I'm on OpenSSH 8.8p1 from Guix System as of yesterday.

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #12, sr #110545 (project administration): [comment #10 comment #10:] > The problem is triggered by the deprecation of SHA1 hashes in the new OpenSSH 8.8 release from last week. Which prevents the host key from being accepted. I am not sure why switching to an ed25519 key

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #11, sr #110545 (project administration): Thanks for the update! I also figured that if ED25519 worked, then that was a net win and I should just go with it. Hope the entanglements aren't too hard to clear up. ___ Reply

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #10, sr #110545 (project administration): The problem is triggered by the deprecation of SHA1 hashes in the new OpenSSH 8.8 release from last week. Which prevents the host key from being accepted. I am not sure why switching to an ed25519 key avoids this. But if that works

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #9, sr #110545 (project administration): [comment #8 comment #8:] > But generally, I hope you can update the OpenSSH of the Git/Mercurial server(s) to avoid other old-version related issues that will inevitably pop up sometime in the future (at least to a version similar to the

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #8, sr #110545 (project administration): Thank you very much Eric! I can confirm that after making an ED25519 key and putting it on Savannah, I was able to push my Git commits to Savannah :-). But generally, I hope you can update the OpenSSH of the Git/Mercurial server(s) to

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #7, sr #110545 (project administration): I had the same issue. I solved it by creating a new ssh key using the ED25519 format and adding it to my account, everything worked fine after that. ___ Reply to this item at:

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #6, sr #110545 (project administration): I am just posting a comment that I am looking at the situation starting now. ___ Reply to this item at:

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #5, sr #110545 (project administration): So what is the nproposed solution to be able to push commits from mercurial / Git? We are blocked. ___ Reply to this item at:

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #4, sr #110545 (project administration): > Can we upgrade the SSH server at Savannah? Some day we shall, probably with the OS, but I have no ETA. ___ Reply to this item at:

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #3, sr #110545 (project administration): I'm hitting the same issue on Mercurial (send_pubkey_test: no mutual signature algorithm). Talking in IRC, seems like the problem might that the client and server versions are way apart (thanks kilobug) Savannah is running SSH server

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #2, sr #110545 (project administration): Thank you very much for the prompt reply. While I was following the debugging steps on the SshAccess page , I noticed that my key gets recognized by the CVS server, but not the SSH

[sr #110545] SSH key not recognized on Git commit

Follow-up Comment #1, sr #110545 (project administration): [comment #0 original submission:] > > $ git push origin master > xx...@git.savannah.gnu.org's password: > These "X...X" are "makhlaghi", aren't they? > Has anything changed on the Savannah Git server in the last few days?

[sr #110545] SSH key not recognized on Git commit

URL: Summary: SSH key not recognized on Git commit Project: Savannah Administration Submitted by: makhlaghi Submitted on: Thu 30 Sep 2021 10:57:15 PM BST Category: Source code