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

safe.directory and ACLs

From
JSJohn Soo <johh.soo@arista.com>
Date
Nov 2, 2022, 15:18 UTC
Message-ID
<CAJyRyRo7oVAfLx8MONO=Y8KhLvL+tJgDTbCUezR1AFa73R5pbw@mail.gmail.com>
Hello git!

We have some build processes that would like access to repos in /home directories that are 0700. We had done this already:

$ setfacl --recursive --modify group:<build users group>:r-X,default:group:<build users group>:r-X /home

Should this ACL be enough to consider the repos "owned" by the build users? Should *any* ACL be enough to consider the repos "owned" by the build users?

Currently: $ sudo -u <build user> git config --get safe.directory $ sudo -u <build user> git -C /home/<non build user>/repo rev-parse HEAD fatal: unsafe repository ('/home/<non build user>/repo' is owned by someone else) To add an exception for this directory, call:

        git config --global --add safe.directory /home/<non build user>
Kindly,
John Soo
Next: brian m. carlson
Message 1 of 5 in “safe.directory and ACLs”
  1. John SooNov 2, 2022
  2. brian m. carlsonNov 2, 2022
  3. John SooNov 2, 2022
  4. Taylor BlauNov 3, 2022
  5. John SooNov 3, 2022

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.