From: Sitaram Chamarty <sitaramc@gmail.com>
To: John McIntyre <joh98.mac@gmail.com>, Heiko Voigt <hvoigt@hvoigt.net>
Cc: git@vger.kernel.org
Subject: Re: Git Server Repository Security?
Date: Tue, 19 May 2015 06:11:44 +0530 [thread overview]
Message-ID: <555A86C8.2020006@gmail.com> (raw)
In-Reply-To: <CABQ4iYgjtdw46Psow_e7uGLqx0ZiFt+TQOgXvCmP1-W10LGEmg@mail.gmail.com>
On 05/18/2015 04:28 PM, John McIntyre wrote:
> 2015-05-18 11:26 GMT+01:00 Heiko Voigt <hvoigt@hvoigt.net>:
>> 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.
>
> That's adding a separate level of complexity.
>
> I looked into filesystem-level permissions. I don't see any means of
> doing so, because everyone accesses the repositories using the 'git'
> user. So even if I add a group like 'devClient1' and then change the
> group ownership of a repo to that user, they'll still be able to
> access all repos..?
My usual answer to this is http://gitolite.com/gitolite/overview.html#basic-use-case
The first example is doable with file system permissions if you give
everyone a separate userid, but it's a nightmare. The second one is not
even possible.
prev parent reply other threads:[~2015-05-19 0:41 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
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 [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=555A86C8.2020006@gmail.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--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 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).