I feel like most practical situations which require this end up just routing through the OS user management and using PAM, but providing git-ssh access is an ob

I feel like most practical situations which require this end up just routing through the OS user management and using PAM, but providing git-ssh access is an obvious case where that's not desirable or even necessarily possible. I'm a bit curious what this ends up meaning for projects like GitLab and Gitea. Gitea's docs [1] indicate that it can either use the system sshd or one that it "provides", but it's not clear whether the provided one is Go-implemented or just a statically-compiled instance that it runs as a subprocess. [1]: https://docs.gitea.io/en-us/faq/#ssh-common-errors https://docs.gitea.io/en-us/faq/#ssh-common-errors