From: "J. Bakshi" <joydeep@infoservices.in>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Restricted git push ?
Date: Tue, 19 Jul 2011 21:36:24 +0530 [thread overview]
Message-ID: <20110719213624.7be7b928@shiva.selfip.org> (raw)
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>
````````````
prev parent reply other threads:[~2011-07-20 6:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 9:36 Restricted git push ? J. Bakshi
2011-07-19 10:05 ` Sitaram Chamarty
2011-07-19 10:33 ` J. Bakshi
2011-07-19 10:45 ` J. Bakshi
2011-07-19 11:10 ` J. Bakshi
2011-07-19 15:03 ` Sitaram Chamarty
2011-07-19 16:06 ` J. Bakshi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110719213624.7be7b928@shiva.selfip.org \
--to=joydeep@infoservices.in \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).