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

Re: Locked down (but still shared) repositories

From
Shawn Pearce <spearce@spearce.org>
Date
Dec 7, 2006, 20:16 UTC
Message-ID
<20061207201625.GA12502@spearce.org>
In-Reply-To
<45786F5A.6020400@dawes.za.net>
Rogan Dawes <discard@dawes.za.net> wrote:
Show 9 quoted lines
> Shawn Pearce wrote:
> >In the situation you describe everyone looks the same to the
> >update hook...
> 
> See Section 8.2.6.1
> 
> http://www.unix.org.ua/orelly/networking_2ndEd/ssh/ch08_02.htm
> 
> You should be able to do something similar for git as they do for SSH.
Ok, I just learned something new.  Thank you!

Forced commands on a per-key basis would certainly work. I'm not settled on the idea as the end solution, but it does seem to be perhaps slightly better than the setuid approach.

Previous: Rogan DawesNext: Randal L. Schwartz
Message 6 of 8 in “Locked down (but still shared) repositories”
  1. Shawn PearceDec 7, 2006
  2. Martin WaitzDec 7, 2006
  3. Johannes SchindelinDec 7, 2006
  4. Shawn PearceDec 7, 2006
  5. Rogan DawesDec 7, 2006
  6. Shawn PearceDec 7, 2006
  7. Randal L. SchwartzDec 7, 2006
  8. Rogan DawesDec 7, 2006

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.