On 2009-05-29 20:38:54, Jeff King <peff@xxxxxxxx> wrote: > On Fri, May 29, 2009 at 01:24:59PM -0700, Paul Tarjan wrote: > >> The reason I need http is slightly convoluted. The remote machine is >> shared hosting with 1 ssh login that I don't want to give to my >> partner AND I don't have root on that box. [snip] > You can let him login via ssh key and restrict the actions of that key > just to running git-upload-pack (which is what "git clone" and "git > fetch" will invoke to clone or fetch commits). Something like: > > command="git-upload-pack /path/to/repo" ssh-rsa ... > > in your .ssh/authorized_keys file. Not that he still won't be able to > actually push (which is maybe what you want). > > For a more featureful solution (with permissions for pushing and pulling > multiple repos), I think gitosis will do what you want (but I have never > used it personally). gitosis is indeed quite featureful. I use it at work to admin about 11 projects with between 1-6 devs and it works very well. All done with ssh pubkey and the "command=" feature of .ssh/authorized_keys that Jeff mentioned above, with a bit of python to read a conf file and decide who is allowed to read/write what repository etc. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html