jcgruenhage/borg-gen-auth-keys
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
No description
4 commits 1 branch 0 tags 76 KiB
Go 100%
Find a file
yJan Christian Grünhage cf6cde36a2
Another README.md change
2017-04-10 18:19:15 +02:00
.gitignore Initial commit 2017-04-10 15:59:14 +00:00
example.json Added source code 2017-04-10 18:04:54 +02:00
LICENSE Initial commit 2017-04-10 15:59:14 +00:00
main.go Added source code 2017-04-10 18:04:54 +02:00
README.md Another README.md change 2017-04-10 18:19:15 +02:00

README.md

Generate an authorized_keys file:

When working with borg serve in an automated environment, you should use an authorized_keys file that restricts the ssh sessions to use only borg, and only in the directory where the repo they should use lies in. This binary takes in a json file specifying the needed info and prints out the wanted authorized_keys file.

To generate that file, do this (assuming you have set up everything needed for go get, and $GOPATH/bin is in your $PATH):

go get git.jcg.re/jcgruenhage/borg-gen-auth-keys.git
borg-gen-auth-keys.git yourjsonfile.json > ~/.ssh/authorized_keys

PS: If anyone could tell me how to get rid of this .git in the end, that would be nice. If someone could tell me, how to make it so that I can put this in a subfolder of another repository, that would be even better (a script collection). At the moment, doing any of those two breaks go get.. Maybe this is something that needs to be fixed in gitea ^^