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

Re: Setting up Password protected repositories?

From
Junio C Hamano <junkio@cox.net>
Date
Sep 17, 2006, 01:24 UTC
Message-ID
<7virjn8eua.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<E1GOktx-0005JY-ER@jdl.com>
Jon Loeliger <jdl@jdl.com> writes:
> git-daemon has to know where to server out the files from,
> but how do we get it to enforce a ssh-based access?  It's
> easy to prevent http: from serving out the repository --
> just place it outside of the webroot directory structure.

It all depends on how you start git-daemon, but the last parameters to git-daemon are path whitelist so presumably placing the private repository outside of it should be enough.

Or am I missing something deeper?
Previous: Jon LoeligerNext: Jon Loeliger
Message 2 of 7 in “Setting up Password protected repositories?”
  1. Jon LoeligerSep 17, 2006
  2. Junio C HamanoSep 17, 2006
  3. Jon LoeligerSep 17, 2006
  4. Junio C HamanoSep 17, 2006
  5. Shawn PearceSep 17, 2006
  6. Jon LoeligerSep 17, 2006
  7. J. Bruce FieldsSep 17, 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.