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

Re: Security and permissions in git

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jan 29, 2009, 22:13 UTC
Message-ID
<alpine.LNX.1.00.0901291645300.19665@iabervon.org>
In-Reply-To
<loom.20090129T203050-865@post.gmane.org>
On Thu, 29 Jan 2009, Jay Renbaum wrote:
> When setting up a public repository is there a way to control who has access 
> to various directories within the repository or is everything equal once you 
> are in?

Every commit contains a version of the complete contents, so people have to be able to read the contents of all directories and write some directory contents. However, you can prohibit users from pushing content to the repository unless particular directories (or files) match what's there already. This is generally what people want when they have this requirement.

It's also possible to use submodules to have a project contain parts that some users don't have any access to, while still being able to produce commits to the main project (in combination with the above check so that try can't replace the submodule entirely with content they do have access to, or submodule commits they've seen referenced previously)

	-Daniel
*This .sig left intentionally blank*
Previous: Jay RenbaumNext: Jeff King
Message 2 of 3 in “Security and permissions in git”
  1. Jay RenbaumJan 29, 2009
  2. Daniel BarkalowJan 29, 2009
  3. Jeff KingJan 29, 2009

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.