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

Re: Security and permissions in git

From
Jeff King <peff@peff.net>
Date
Jan 29, 2009, 23:23 UTC
Message-ID
<20090129232358.GA12941@coredump.intra.peff.net>
In-Reply-To
<alpine.LNX.1.00.0901291645300.19665@iabervon.org>
On Thu, Jan 29, 2009 at 05:13:41PM -0500, Daniel Barkalow wrote:
Show 6 quoted lines
> 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.

If this is what you want, see Shawn's contrib/hooks/update-paranoid, which lets you specify ACLs in the config.

-Peff
Previous: Daniel Barkalow
Message 3 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.