Hey #gitea instance admins. Do you have SSH for your Gitea instance enabled via OpenSSH? Then be aware that you should add `AcceptEnv GIT_PROTOCOL` to your `/etc/ssh/sshd_config` file! This enables Git Wire Protocol v2 for Git over SSH.
If you're using Gitea's Internal SSH Server, this behavior will be enabled in v1.17.1
Boost are are welcome for awareness.
@emacsen you can run a SSH server without using OpenSSH, the Gitea binary comes included with one. You can enable it by setting `START_SSH_SERVER = true` under the `[server]` section https://docs.gitea.io/en-us/config-cheat-sheet/#server-server . Using the internal SSH Server will automatically have this new behavior from 1.17.1(currently not released) and onwards.
@emacsen Go's SSH code lacks certain new cryptographic algorithms and it lacks behind on certain SSH RFCs. This cause annoying bugs with OpenSSH clients, which uses up-to-date SSH protocol standards, the most notorious example is https://github.com/go-gitea/gitea/issues/17798 . It's usually used when the machine doesn't have the agility to use OpenSSH.
@michael Are you running Gitea in docker?
You don't need any changes in app.ini, if you're using the OpenSSH server(so the sshd daemon) then you need to append `AcceptEnv GIT_PROTOCOL` to your `/etc/ssh/sshd_config` file. But if you're using the SSH Internal Server, you just need to wait until 1.17.1 is released.
@michael Looking at your screenshot it seems you're using the OpenSSH server. Yes it does say that Git support the Wire V2 protocol, however currently when using Git over SSH the information that the Git client also support Wire V2 protocol isn't passed trough.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!