git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Repository Security

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 23, 2007, 14:29 UTC
Message-ID
<Pine.LNX.4.63.0701231525250.22628@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<200701230823.17938.andre@masella.no-ip.org>
Hi,
On Tue, 23 Jan 2007, Andre Masella wrote:
Show 8 quoted lines
> > > As I understand it, none of the repository backends allow any per-user
> > > per-branch access control.
> > The idea in git (unless you really want to get the same setup as in CVS,
> > which would be rather sad) is that every developer has at least one
> > repository. Write-access: only one developer.
> 
> Believe me: I was ready to throw a party when I got to shutdown CVS last 
> week.
Congratulations!
Show 5 quoted lines
> Say I have two utterly separate repositories with two integrators. I 
> want to put them on a web server (and so same DAV share). There is 
> little to stop the integrator of one project (by intention or accident) 
> from modifying the other repository. It can be done, but doing it 
> requires one section of the httpd.conf per repository.
I thought you can do all the fancy WebDAV stuff with .htaccess?
Show 7 quoted lines
> > I already hear the complaint: "But you need a central repository!". If 
> > you _have_ to have a central repository, designate the integrator's 
> > repository central.
> 
> Okay, say one regular developer wants share his changes with another 
> developer. He either has to mail patches, create an SSH account, or set 
> up one of git-daemon or WebDAV.

Most likely just start git-daemon. It's read-only (in the future, you might be able to enable anonymous push, but not right now), so you don't have to worry.

> And most of those require knowing the workstation name which is 
> inconvienient.
Umm. Oh. Okay. Didn't expect _that_ to be inconvenient.
> I would rather have each user able to push to a branch with their name 
> on it on a central server.

Really, the easiest is to setup a central server with SSH, where every user has an individual account. Administrating, say, a Linux box with literally thousands of users is a charm.

Ciao, Dscho

Previous: Andre MasellaNext: Andy Parkins
Message 7 of 13 in “Repository Security”
  1. Andre MasellaJan 22, 2007
  2. Shawn O. PearceJan 22, 2007
  3. Andre MasellaJan 23, 2007
  4. Martin LanghoffJan 22, 2007
  5. Johannes SchindelinJan 23, 2007
  6. Andre MasellaJan 23, 2007
  7. Johannes SchindelinJan 23, 2007
  8. Andy ParkinsJan 23, 2007
  9. Jakub NarebskiJan 23, 2007
  10. Andre MasellaJan 23, 2007
  11. Johannes SchindelinJan 23, 2007
  12. Andreas EricssonJan 24, 2007
  13. Linus TorvaldsJan 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.