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

Re: Repository Security

From
Jakub Narebski <jnareb@gmail.com>
Date
Jan 23, 2007, 11:06 UTC
Message-ID
<ep4q5e$ioc$1@sea.gmane.org>
In-Reply-To
<200701221433.13257.andre@masella.no-ip.org>
Andre Masella wrote:
Show 7 quoted lines
> I've been using git for a while and really like it, but I have a concern about 
> security.
> 
> 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.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Andy ParkinsNext: Andre Masella
Message 9 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.