search

deian / git-ssh-server

SSH server for handling git-{upload,receive}-pack with custom authentication
22 stars 6 forks source link

Using server's authorized_keys #3

Open OmgImAlexis opened 7 years ago

OmgImAlexis commented 7 years ago

Is it possible to use the authorized_keys file from the current user instead of having a seperate on inside of the config dir?

For example ~/.ssh/authorized_keys

deian commented 7 years ago

Ah that should be easy enough to implement. It's been a while, but reading my own readme I think we create a keys/authorized_keys file anyway. You can hack this up to either symlink to ~/.ssh/authorized_keys or write a custom authorization implementation. I'd be happy to merge it in, but don't have the time to hack on this myself.

OmgImAlexis commented 7 years ago

Okay I'll look into it.

OmgImAlexis commented 7 years ago

Is there a way to add stuff to the config.json without the server overriding it on launch? I need to add something like this. That way if auto is true we use their system file if auto is false we use the path provided. The problem I've got is that every time I launch it config.json gets reset.

 "authorized_keys": {
     "auto": true,
     "path": "~/.ssh/authorized_keys"
 }
deian commented 7 years ago

Really? Are you passing in arguments that are then used to rewrite the json file?

I think adding another option to modify the sshd_config to not generate authorized_keys file is probably the simpler way to go. This would require changes to the sshd_config template file (in addition). You can temporarily hack this up manually by modifying the sshd_config file to point to your ~/.ssh/authorized_keys file too btw: https://github.com/deian/git-ssh-server/blob/master/templates/sshd_config#L13