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

Re: Re: [PATCH] Add USER environment variable to executed git commands when serving

From
Shawn O. Pearce <spearce@spearce.org>
Date
Jun 3, 2009, 21:02 UTC
Message-ID
<20090603210201.GP3355@spearce.org>
In-Reply-To
<robbat2-20090603T204719-922480112Z@orbis-terrarum.net>
"Robin H. Johnson" <robbat2@gentoo.org> wrote:
Show 9 quoted lines
> On Wed, Jun 03, 2009 at 10:27:02PM +0200, Heiko Voigt wrote:
> > You are welcome. An interesting addition would be to propagate allowed
> > branchnames from gitosis.conf. That way you can implement write-
> > protected branches using an update hook.
> ...
> > A nice solution to steer this directly from gitosis.conf? I never got
> > around implementing it.
> Has anybody implemented something like cvs_acls.pl (used by FreeBSD) for
> Git?
contrib/hooks/update-paranoid ?

Perhaps the most flexible, and most paranoid, update hook available. But it does require that the frontend set some sort of user identity. I think it relies on UNIX uid, but its easy to hack to use an env var instead from gitosis.

-- 
Shawn.
Previous: Robin H. Johnson
Message 11 of 11 in “gitosis question: identifying/logging remote user”
  1. Sitaram ChamartyJun 2, 2009
  2. Robin H. JohnsonJun 2, 2009
  3. Sitaram ChamartyJun 2, 2009
  4. Robin H. JohnsonJun 2, 2009
  5. Sitaram ChamartyJun 3, 2009
  6. Add USER environment variable to executed git commands when servingHeiko Voigt, Jun 2, 2009
  7. Sitaram ChamartyJun 3, 2009
  8. Sitaram ChamartyJun 3, 2009
  9. Heiko VoigtJun 3, 2009
  10. Robin H. JohnsonJun 3, 2009
  11. Shawn O. PearceJun 3, 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.