git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gelonida <gelonida@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git push from bare repo
Date: Sat, 29 May 2010 13:01:57 +0200	[thread overview]
Message-ID: <htqs75$tco$1@dough.gmane.org> (raw)
In-Reply-To: <36AD1DE8-9E28-4373-94CF-72E88ABBB309@bjhargrave.com>

BJ Hargrave wrote:
> On May 28, 2010, at 08:28 , Goran Mekić wrote:
>>    There's more then one developer and 600 is set to just one user.
>> Post-receive hook is executed as developer doing push. The accounts are in
>> LDAP, but I can't set all their UID number to same number because it's
>> used
>> for PAM. I was thinking about ACL. Is that even a solution? The dumb one
>> would be cron, but I wish I avoid pushing when there's no change.
>>
> 
> What about having a script which does the push have setuid to the owner of the key. Then the post-receive hook can invoke that script which will have access to the ssh key to do the push.
That should work.


another option would be, that the post receive hook copies the ssh-key
file, changes its permission andcontinues only then to push.


If all users have ssh access to first server AND to second server and
all users use ssh-agent, then all users had just to make sure, that they
do agent forwarding in their .ssh/config script.

      reply	other threads:[~2010-05-29 11:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  6:57 Git push from bare repo Goran Mekić
2010-05-28  9:15 ` Andreas Ericsson
2010-05-28 12:28   ` Goran Mekić
2010-05-28 12:59     ` BJ Hargrave
2010-05-29 11:01       ` Gelonida [this message]

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='htqs75$tco$1@dough.gmane.org' \
    --to=gelonida@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).