git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git push from bare repo

From
GGelonida <gelonida@gmail.com>
Date
May 29, 2010, 11:01 UTC
Message-ID
<htqs75$tco$1@dough.gmane.org>
In-Reply-To
<36AD1DE8-9E28-4373-94CF-72E88ABBB309@bjhargrave.com>
BJ Hargrave wrote:
Show 10 quoted lines
> 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.

Previous: BJ Hargrave
Message 5 of 5 in “Git push from bare repo”
  1. Goran MekićMay 28, 2010
  2. Andreas EricssonMay 28, 2010
  3. Goran MekićMay 28, 2010
  4. BJ HargraveMay 28, 2010
  5. GelonidaMay 29, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.