Not sure yet how to solve it properly, but by tailing the logs of my Gitea server, at least I figured out why I could login via command line using my system SSH, but SmartGit was failing with the "Exhausted available authentication methods" error. That includes the one I've been using for a number of years, and apparently SmartGit is not passing the correct parameters to force the SSH client to accept them. Older ssh keys were often created with that encryption. This is related to the recent changes in OpenSSH where PubkeyAcceptedAlgorithms no longer includes the ssh-rsa algorithm. I'm on the hunt for the solution for me as well. SmartGit still works except for interacting with the remote server so I'm switching tools all the time now to get stuff done. Git on the command line via GitBash does currently work with my current SSH key. I know my SmartGit isn't the current version since my upgrade support ran out last year. I do know that the error is coming from SSH. I tried to completely uninstall and reinstall SmartGit (including clearing out appdata folder), I don't think it uses Windows Registry, but I'm still getting the error. Using Git via Gitbash works just fine with the current SSH keys. However, I also started to get a "Exhausted Available Authentication Methods" error when I tried to pull. I was getting a warning about the SSH fingerprint change, so I went in and cleared out my known hosts file. I access with SmartGit and use SSH keys for authentication. I believe that they moved it to a different machine.
A few days ago, a Git server (using Gitlab) I work on had some changes made and went down for a while.
0 kommentar(er)
