Re: Git and securing a repository

On Jan 2, 2008 2:13 AM, Gonzalo Garramuño [off-list ref] wrote:

I've been using git for some time and love it.  For open source projects
there's clearly nothing currently better.

However, I am now using git for proprietary elements, which in the
future I may need or want to partially restrict access to.  The idea
being that at my company some (junior) developers should not be given
access to some elements.  That means either that some full git
repository should be password protected or even portions of the same
repository.

Another desirable way to protect elements might be only giving
clone/pull access to a repository (or portion of it) but not permissions
to push in changes.

push access is only available through ssh, so if your developer
doesn't have a ssh account on the server, he can't push code to it

I have not seen or read much about how git deals with accesses and
permissions.  Can anyone point me to some documentation if some or all
of this is possible?

it's easy on the full repository case, create different groups and
share git repositories by groups, after that chmod o-rwx -R
/path/to/repository.git.

If a user is not the owner nor is part of that group in particular, it
wouldn't be able to push any code to the repository.

btw, if you don't start git-daemon you could use ssh to pull code as well.

thinking on the partial repository access, maybe git submodule would
help, but i've never used it.

-- 
Best Regards,

Felipe Balbi
felipebalbi@users.sourceforge.net