-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH Authorization #8
SSH Authorization #8
Conversation
requires a designated user and chmod +x for that user on git-shell keyManager could use work on users who have existing authorized_keys file
Can I merge this now and take it over, or do you still want to do more work? |
I made a little bit of progress today, got to the point where git client I can push that when I get back to my computer as another branch or
|
I managed to get this to work now :D |
…s to package.json, cleaned up keyManager and included fixes for paths with spaces, keymanager now correctly adds keys to authorized_keys
Just managed to figure out what was going on with streams and now this no longer requires kexec. I'm thinking the best way to notify the server about commit events is probably just a post-receive hook for each repo. |
Basic building blocks for ssh authentication/authorization, still early alpha but with this I can at least: