git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Krey <a.krey@gmx.de>
To: Grant <emailgrant@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Does git have "Path-Based Authorization"?
Date: Sun, 2 Oct 2011 08:38:57 +0200	[thread overview]
Message-ID: <20111002063857.GA9385@inner.h.iocl.org> (raw)
In-Reply-To: <CAN0CFw3ZDcXtD7WChjkT1Vg0cU_u==4KCHo8ff-ccbyxZ8xWjg@mail.gmail.com>

On Sat, 01 Oct 2011 20:34:43 +0000, Grant wrote:
...
> That's true.  I hope to be able to give different developers access to
> different parts of the code.  I really don't know if this will work.

Depending on the implementation it may drive away the good devs...

Anyway, what I think you need (for the reasons detailed in the svn list)
is a setup where the whole project is checked out in the staging area
where it can be tested in whatever way. That under a user id different
from the dev's. Then you change permissions so that he can only see
and edit the files you want him to. This at least eases the problem
of having to commit for each test, and gives you a meaningful history.
Additionally have sudo permissions to do commits etc. in the staging area.

(But still the dev's life will be, erm, suboptimal.)

> I just don't want my code to be stolen and I'm trying to find some way
> to prevent that from happening.

I'm just getting creative. When the one file that you allow access to
is server-side code (as opposed to, say, css or client js) then the
malevolent dev can use that to read the rest of the staging area anyway.

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800

  reply	other threads:[~2011-10-02  6:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 23:43 Does git have "Path-Based Authorization"? Grant
2011-10-01  0:05 ` Carlos Martín Nieto
2011-10-01  1:31   ` Grant
2011-10-01  1:34     ` Nguyen Thai Ngoc Duy
2011-10-01  1:43       ` Grant
2011-10-01  2:09         ` david
2011-10-01 13:06 ` Jakub Narebski
2011-10-02  0:00   ` Grant
2011-10-02  1:27     ` Sitaram Chamarty
2011-10-02  2:53       ` Grant
2011-10-02  3:24         ` Nguyen Thai Ngoc Duy
2011-10-02  3:34           ` Grant
2011-10-02  6:38             ` Andreas Krey [this message]
2011-10-02  6:43             ` Frans Klaver
2011-10-02 14:50               ` Enrico Weigelt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111002063857.GA9385@inner.h.iocl.org \
    --to=a.krey@gmx.de \
    --cc=emailgrant@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).