Re: sharedrepository=group not working

On Mon, Dec 03, 2018 at 07:27:13PM -0800, Jamie Zawinski wrote:

Hmm. Given the time-frame and the fact that your strace shows problems writing into the objects/incoming-* directory, it's likely caused by 722ff7f876 (receive-pack: quarantine objects until pre-receive accepts, 2016-10-03).

The big change there is that instead of writing directly into objects/, we create a temporary objects/incoming-* directory, write there, and then migrate the objects over after we determine they're sane.

So in your strace we see the temp directory get created:

The permissions are tighter than we ultimately want, but that's OK. This tempdir is just for this process (and its children) to look at, and then we'd eventually migrate the files out.

I could definitely imagine there being a bug in which we don't then properly loosen permissions when we move things out of the tempdir, but we don't even get that far. We fail immediately:

That seems strange. The outer directory is only 0700, but the user permissions should be sufficient. Even with the g+s bit set, it should still be owned by the same user, shouldn't it?

I tried reproducing your state like this:

  git init --bare dst.git
  git -C dst.git config core.sharedrepository group
  chgrp -R somegroup dst.git
  find dst.git -type f | xargs chmod g+rw
  find dst.git -type d | xargs chmod g+srw

  # push works from original user
  git clone dst.git client
  (
    cd client &&
    git commit --allow-empty -m foo
    git push
  )

  # push works from alternate user
  sudo su anotheruser sh -c '
    git clone dst.git /tmp/other &&
    cd /tmp/other &&
    git commit --allow-empty -m foo &&
    git push --receive-pack="strace -e mkdir git-receive-pack"
  '

but it works fine. Might there be some effective-uid trickiness with the way the server side of git is invoked? Or is this a network mount where the filesystem uid might not match the process uid?

-Peff