public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Shawn Pearce <spearce@spearce•org>
To: Jon Loeliger <jdl@jdl•com>
Cc: Junio C Hamano <junkio@cox•net>, git@vger•kernel.org
Subject: Re: Setting up Password protected repositories?
Date: Sat, 16 Sep 2006 22:20:14 -0400	[thread overview]
Message-ID: <20060917022013.GA7512@spearce.org> (raw)
In-Reply-To: <E1GOm3h-0005jq-5u@jdl.com>

Jon Loeliger <jdl@jdl•com> wrote:
> So, like, the other day Junio C Hamano mumbled:
> > 
> > It all depends on how you start git-daemon, but the last
> > parameters to git-daemon are path whitelist so presumably
> > placing the private repository outside of it should be enough.
> > 
> > Or am I missing something deeper?
> 
> I want git-daemon to serve up the repository.
> I just want to have it served to people who can
> supply a password or have an ssh key in place.

Don't use git-daemon.

Instead create UNIX accounts for the people who need access and if
you don't want them to actually be able to login set their shell
to be `git-sh`.  This is a special shell-like thing that only lets
the user push or fetch to any repository they have access to.

The URL is a 'git+ssh' style URL and they will use SSH to connect.

Access is controlled by standard UNIX user/group read/write access
and ACLs if your OS/filesystem support them.  You can also control
pushing with an update hook.

-- 
Shawn.

  parent reply	other threads:[~2006-09-17  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  0:52 Setting up Password protected repositories? Jon Loeliger
2006-09-17  1:24 ` Junio C Hamano
2006-09-17  2:07   ` Jon Loeliger
2006-09-17  2:18     ` Junio C Hamano
2006-09-17  2:20     ` Shawn Pearce [this message]
2006-09-17 16:22       ` Jon Loeliger
2006-09-17 16:43         ` J. Bruce Fields

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=20060917022013.GA7512@spearce.org \
    --to=spearce@spearce$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    --cc=jdl@jdl$(echo .)com \
    --cc=junkio@cox$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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