From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: Repository Security
Date: Tue, 23 Jan 2007 12:06:09 +0100 [thread overview]
Message-ID: <ep4q5e$ioc$1@sea.gmane.org> (raw)
In-Reply-To: 200701221433.13257.andre@masella.no-ip.org
Andre Masella wrote:
> I've been using git for a while and really like it, but I have a concern about
> security.
>
> As I understand it, none of the repository backends allow any per-user
> per-branch access control. SSH and HTTP come the closest with the right
> hooks, but since the repository is writeable by those users, there is little
> to stop them from changing the repository directly.
I wonder if it would be enought for SSH (and perhaps HTTP/WebDAV access)
just to rely on filesystem write access to refs/heads files (different
files having different access rights), and filesystem ACLs.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-23 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 19:33 Repository Security Andre Masella
2007-01-22 20:53 ` Shawn O. Pearce
2007-01-23 13:23 ` Andre Masella
2007-01-22 23:46 ` Martin Langhoff
2007-01-23 9:41 ` Johannes Schindelin
2007-01-23 13:23 ` Andre Masella
2007-01-23 14:29 ` Johannes Schindelin
2007-01-23 15:00 ` Andy Parkins
2007-01-23 11:06 ` Jakub Narebski [this message]
2007-01-23 13:23 ` Andre Masella
2007-01-23 21:38 ` Johannes Schindelin
2007-01-24 9:31 ` Andreas Ericsson
2007-01-23 16:18 ` Linus Torvalds
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='ep4q5e$ioc$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.