3 ms·
If I recall Gitea can run its owns libssh instance on a different port, and requires manually importing keys for each user. If you are using the https interfac
by Joel_Mckay 4y ago
If I recall Gitea can run its owns libssh instance on a different port, and requires manually importing keys for each user. If you are using the https interface by default, than one may need to explicitly use the ssh:// uri.
Gitea should not be exposed to the web, and a port knock sequence is highly recommended to keep private projects private. ;)
- nyanpasu64 4y agoI'm running Gitea in my LAN only, and currently hiding behind Tailscale (only listening to the Tailscale IP for HTTP, forgot to set that up for SSH over a custom port but that's not really a vulnerability) rather than exposed to other LAN devices. I may open it up to my full LAN in the future, I haven't decided.
- Joel_Mckay 4y agoAnother issue with Gitea we found was memory requirements are somewhat unclear. So if you have to version large binary images in a source tree, the daemon can develop a number of hard to diagnose failure modes. It may sound ridiculous, but make sure you have at least 4GiB of free ram. Most of the time it will never be used, but it is far better than chasing ghost issue for that edge case where it does. ;)