commit 6736d870dd7bf83a4f067db3116abc10cb9b5d21 parent ab995e6fa12b53f98932378cff895a5d731e52c0 Author: parazyd <parazyd@dyne.org> Date: Wed, 31 Mar 2021 03:34:52 +0200 Add manpage. Diffstat:
| A | git-restrict.1 | | | 31 | +++++++++++++++++++++++++++++++ |
1 file changed, 31 insertions(+), 0 deletions(-)
diff --git a/git-restrict.1 b/git-restrict.1 @@ -0,0 +1,31 @@ +.TH GIT-RESTRICT 1 2021-03-31 +.SH NAME +git-restrict +.SH SYNOPSIS +.B git-restrict +.IR repository0 +.IR repository1 ... +.PP +.SH DESCRIPTION +git-restrict is a minimal utility that allows repository permission +management based on ssh keys when used in the command directive in +ssh's authorized_keys format. If used, it will only allow +.B git-upload-pack +and +.B git-receive-pack +as the commands allowed to be ran by a specific user/SSH key. +.TP +.SS Basic usage: +.Bd -literal + + $ cat ~/.ssh/authorized_keys + command="/usr/bin/git-restrict repo0 repo1 repo2" ssh-ed25519 AAA...1 user0@machine + command="/usr/bin/git-restrict repo3 repo0" ssh-ed25519 AAA.Z user1@machine + +It is also useful to see the +.B contrib +directory to see an automation example. +.SH AUTHORS +Ivan J. <parazyd@dyne.org> +.SH LICENSE +GNU Affero General Public License version 3