3 ms·
> by any cloud provider I don't care much for cloud providers adding unnecessary restrictions, so I manage my own sshd_config on VMs. I'd like to rent a flat,
by pritambaral 5y ago
> by any cloud provider
I don't care much for cloud providers adding unnecessary restrictions, so I manage my own sshd_config on VMs. I'd like to rent a flat, not a hotel room, thank you very much.
> Git hosting platform
It appears GitLab, one of my platforms of choice, does support this in self-hosted setups[1]. Even if they didn't, it'd be trivial to extend their sshd_config by myself anyway.
1: https://docs.gitlab.com/ee/administration/operations/ssh_certificates.html https://docs.gitlab.com/ee/administration/operations/ssh_cer...
- remram 5y agoIt is true that you are free to change the config on a VM manually. I included it because it's the only other service I could think of where you might set up SSH authentication. This is interesting about GitLab, thanks for the pointer. As you mentioned it only appears to be configurable instance-wide, there is no way for a user or organization to set it up for themselves (for example for your gitlab.com organization). That makes it a bad replacement for SyncThing'd private keys as moviuro suggested.