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

Setting up Password protected repositories?

From
Jon Loeliger <jdl@jdl.com>
Date
Sep 17, 2006, 00:52 UTC
Message-ID
<E1GOktx-0005JY-ER@jdl.com>

So at the risk of asking a dead-stupid question for which I should likely be soundly beaten for even asking...

How does one set up a git repository on a public site but password/ssh protected it so that only a few trusted people can access and update it?

Clearly, we should be using ssh+git: here somehow, right? 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.

I can already enforce pushes to be password protected, but the protection on pulls and clones eludes me. I'd also like to NOT grant login shell access on the repository server machine, so I'm envisioning placing pubic keys from trusted people somewhere too...

I feel like I am being blindly stupid here.
Any help for the weary?

Thanks, jdl

Next: Junio C Hamano
Message 1 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.