From: Andre Masella <andre@masella.no-ip.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Repository Security
Date: Tue, 23 Jan 2007 08:23:19 -0500 [thread overview]
Message-ID: <200701230823.20061.andre@masella.no-ip.org> (raw)
In-Reply-To: <ep4q5e$ioc$1@sea.gmane.org>
> > 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.
It could probably be done, but it would be very complicated. For instance, if
a user is allowed to run prune, then they must have permissions to delete
files which would include any of the objects.
For DAV, this breaks down completely because all access to the repository will
happen as the Apache user.
--
--Andre Masella (andre at masella.no-ip.org)
next prev parent reply other threads:[~2007-01-23 21:16 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
2007-01-23 13:23 ` Andre Masella [this message]
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=200701230823.20061.andre@masella.no-ip.org \
--to=andre@masella.no-ip.org \
--cc=git@vger.kernel.org \
--cc=jnareb@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).