All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Voigt <hvoigt@hvoigt.net>
To: John McIntyre <joh98.mac@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git Server Repository Security?
Date: Mon, 18 May 2015 12:26:33 +0200	[thread overview]
Message-ID: <20150518102633.GA15186@book.hvoigt.net> (raw)
In-Reply-To: <CABQ4iYiWu17H1XhPYebmP27x=R11SKW0P91AW2y9S=r-2c0B1A@mail.gmail.com>

Hi,

On Mon, May 18, 2015 at 11:07:02AM +0100, John McIntyre wrote:
> Hi,
> I've been asked to set up a git repository for a few projects.  So I
> have a Linux CentOS server running git.   I place the repositories
> under /opt and I use the .ssh/authorized_keys of the git user, to
> grant access. The user sends me his private key, and I paste it into
> the end of the file.
> 
> And now, I realise that there's a problem.  If I have /opt/repo1.git
> and /opt/repo2.git, then all users can access both repositories.
> 
> Is there a way to prevent this?

If you want a simple tool using ssh-keys have a look at gitolite[1].
It quite simple to setup and with it you can specify all kinds of access
rights.

Cheers Heiko

[1] http://gitolite.com/gitolite/index.html

  reply	other threads:[~2015-05-18 10:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18 10:07 Git Server Repository Security? John McIntyre
2015-05-18 10:26 ` Heiko Voigt [this message]
2015-05-18 10:58   ` John McIntyre
2015-05-18 11:57     ` Heiko Voigt
2015-05-18 12:32       ` John McIntyre
2015-05-18 12:39         ` Heiko Voigt
2015-05-18 15:07           ` John McIntyre
2015-05-18 19:15             ` Kevin Daudt
2015-05-19  0:35         ` Sitaram Chamarty
2015-05-18 12:18     ` Jason Cooper
2015-05-19  0:41     ` Sitaram Chamarty

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=20150518102633.GA15186@book.hvoigt.net \
    --to=hvoigt@hvoigt.net \
    --cc=git@vger.kernel.org \
    --cc=joh98.mac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.