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

Re: Repository Security

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jan 22, 2007, 23:46 UTC
Message-ID
<46a038f90701221546n7a956a31n936aacb1c979730e@mail.gmail.com>
In-Reply-To
<200701221433.13257.andre@masella.no-ip.org>
On 1/23/07, Andre Masella <andre@masella.no-ip.org> wrote:
> 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.

For this kind of scenario, use one repo per developer with GIT+SSH. It changes your usage pattern slightly (pull from all repos before push) but this is easy to setup. And you can even enforce the "won't let you push unless you are up-to-date with the other repositories" via a fancy pre-update hook script on the repo.

Or you may chose to have an integration repo _as well_ as public per-dev repos.
> So, before I start, I would like to get ideas from others...or be told this is
> a waste of time. Thanks.

Not entirely a waste of time, but there is a very git-style way of addressing this that will probably save you time...

martin
Previous: Andre MasellaNext: Johannes Schindelin
Message 4 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.