From: J. Bakshi <joydeep@infoservices.in>
Date: Tue, 19 Jul 2011 16:06:24 GMT
Subject: Re: Restricted git push ?
Message-ID: <20110719213624.7be7b928@shiva.selfip.org>
In-Reply-To: <CAMK1S_hhHhETL2tE=E98Bku96KULC9L-pHCwz3iPjwEcMbCe9w@mail.gmail.com>

On Tue, 19 Jul 2011 20:33:23 +0530
Sitaram Chamarty <sitaramc@gmail.com> wrote:

> On Tue, Jul 19, 2011 at 4:40 PM, J. Bakshi <joydeep@infoservices.in> wrote:
> 
> > Just like git-receive-pack anything for git pull,clone etc.. ? then we can use those to restrict read access separately. Users having read access need not have the right access then.
> 
> git-upload-pack I guess.  Maybe git-upload-archive also.
> 

I have tried with git-upload-pack, but it gives error as

````````````
Cloning into ....
error: RPC failed; result=22, HTTP code = 401
fatal: The remote end hung up unexpectedly
````````````````

The configuration I use is

````````````
<LocationMatch "^/git/.*/git-upload-pack$">
AuthType Basic
# Message to give to the committer
AuthName "Write access requires a password"
# File listing users with write (commit) access
AuthUserFile /home/git/pushACL
Require valid-user
</LocationMatch>
````````````