You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The built-in SSH server is useful, especially for testing. The biggest disadvantage is that the user shown in the UI for the built-in SSH server is set to whatever the RUN_USER is set to, which must be the user Gitea is started as.
In my opinion, there should be a config option to set a custom user to display in the UI in the SSH clone URL when the built-in SSH server is enabled. There could also be an option to omit the user entirely, because any user will work, as long as the SSH key is registered in the user's settings.
The text was updated successfully, but these errors were encountered:
* Allow custom SSH user in UI for built-in SSH server (#2617)
* Some fixes
* Did make fmt
* Updated according to review
- Renamed config to BUILTIN_SSH_SERVER_USER
- Removed unnecessary default string value for config item
* Updated according to review
* Fixed some minor issues
The built-in SSH server is useful, especially for testing. The biggest disadvantage is that the user shown in the UI for the built-in SSH server is set to whatever the
RUN_USER
is set to, which must be the user Gitea is started as.Because the built-in SSH server only uses the public-key to authenticate, I can use any user when cloning the repository.
In my opinion, there should be a config option to set a custom user to display in the UI in the SSH clone URL when the built-in SSH server is enabled. There could also be an option to omit the user entirely, because any user will work, as long as the SSH key is registered in the user's settings.
The text was updated successfully, but these errors were encountered: