git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Restricted git push ?

From
JBJ. Bakshi <joydeep@infoservices.in>
Date
Jul 19, 2011, 16:06 UTC
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:

Show 6 quoted lines
> 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> ````````````

Previous: Sitaram Chamarty
Message 7 of 7 in “Restricted git push ?”
  1. J. BakshiJul 19, 2011
  2. Sitaram ChamartyJul 19, 2011
  3. J. BakshiJul 19, 2011
  4. J. BakshiJul 19, 2011
  5. J. BakshiJul 19, 2011
  6. Sitaram ChamartyJul 19, 2011
  7. J. BakshiJul 19, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.