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

Re: Repository Security

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Jan 23, 2007, 16:18 UTC
Message-ID
<Pine.LNX.4.64.0701230817010.32200@woody.linux-foundation.org>
In-Reply-To
<ep4q5e$ioc$1@sea.gmane.org>
On Tue, 23 Jan 2007, Jakub Narebski wrote:
> 
> 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.
I think the solution is simple: mark the refs/ directory as being sticky.

This is really no different from the /var/spool/mail/ situation: people want to change their own files (and create new files), but you can't allow people to overwrite other peoples files and filenames.

		Linus
Previous: Andreas Ericsson
Message 13 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.