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

Re: Locked down (but still shared) repositories

From
Martin Waitz <tali@admingilde.org>
Date
Dec 7, 2006, 12:21 UTC
Message-ID
<20061207122111.GD10468@admingilde.org>
In-Reply-To
<20061207113539.GA10781@spearce.org>
hoi :)
On Thu, Dec 07, 2006 at 06:35:39AM -0500, Shawn Pearce wrote:
Show 5 quoted lines
> So I've patched git-receive-pack to refuse to run if its running
> setuid and the hook's owner isn't the effective uid, or the hook
> is group/world writable.  This seems to close the last hole, but
> it also makes hooks/update and hooks/post-update useless in user
> private repositories on this system.

perhaps don't refuse to run, but simply change back to the safed uid? Or use one special machine which hosts the repository and which has the modified version of git installed.

-- 
Martin Waitz
Previous: Shawn PearceNext: Johannes Schindelin
Message 2 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.