Re: Permissions and authorisations in git repository

* Konstantin Khomoutov <flatworm@users.sourceforge.net> wrote:

<snip>

In fact, git does not have any access control whatsoever. It relies on what the underlying transport protocol allows it to do.

With ssh, you could wrap the commands into some script which checks, the permissions on calling-in user or key (eg. restrict write access on certain refs to certain people). You could do even more fancy things like given everybody (or certain people) unrestricted write access, but under the hood put their rename the updated refs (eg. you can push 'master', but on the server, refs/heads/master wont be overwritten, instead it goes to refs/heads/konstantin/master).

Some people (coming from strictly-central ideologies) might consider git's access control angonsticity a drawback, but IMHO it's a very good thing - git doesn't want to be a full-blown "out-of-the-box" VCS (like, eg. clearcase), but more a lightweight toolkit to easily build your own.

cu