| 1 |
On 04/09/2017 17:20, Simon Thelen wrote: |
| 2 |
> On 17-09-04 at 17:05, Alan McKinnon wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> I fear I have a severe case of too many trees in the way to see the forest. |
| 6 |
>> |
| 7 |
>> I have a git server, it only runs git. |
| 8 |
>> All the sysadmins have full access using ssh://, their keys are in git's |
| 9 |
>> authorized_keys, the repos are owned git:git, MODE 770, etc etc, and it |
| 10 |
>> works like it should. |
| 11 |
>> |
| 12 |
>> I want an app to have read-only access to some repos, i.e. clone and |
| 13 |
>> pull only. But they are not publicly accessible i.e. the app user must |
| 14 |
>> be pre-authorized by me and have a public key. And for the life of me I |
| 15 |
>> can't think how to do it! |
| 16 |
> You want to use the command= option in the .ssh/authorized_keys file for |
| 17 |
> the key to ensure that only `git-upload-pack <repo_path>' is run |
| 18 |
> |
| 19 |
>> Google is only giving me results about what fancy buttons to click in |
| 20 |
>> GitHub and Gitlab... I know, my Google-fu sucks today. |
| 21 |
> You can look at [1] if you want a really minimal example of a git |
| 22 |
> permissions management system. |
| 23 |
> |
| 24 |
> [1]: https://github.com/cbdevnet/fugit |
| 25 |
> |
| 26 |
|
| 27 |
|
| 28 |
available options: push/pull/nothing |
| 29 |
|
| 30 |
well, that's my needs-spec exactly :-) |
| 31 |
|
| 32 |
thanks for the link, I'll check it out later |
| 33 |
|
| 34 |
-- |
| 35 |
Alan McKinnon |
| 36 |
alan.mckinnon@×××××.com |
Archives