On Fri, Nov 7, 2014 at 2:39 AM, Jonathan Nieder <jrnie...@gmail.com> wrote: > tags 768359 + upstream patch fixed-upstream > quit > > Hi, > > anatoly techtonik wrote: > >> git clone unconditionally creates main dir with 755 >> mode ignoring ACL and POSIX permissions if they >> are different. >> >> More info here: >> https://stackoverflow.com/questions/10637416/git-clone-respects-umask-except-for-top-level-project-directory >> >> Fix is available in 1.7.11.3 commit > > Thanks for a clear report. > > [...] >> Severity: important > > Can you say a little more about this? The old behavior of using > (0755 & ~umask) instead of (0777 & ~umask) wouldn't be a security > problem, making a worktree shared within a group tends to require > writing the setgid ("sticky") bit anyway, and using chmod once works > as a workaround. > > So it seems like a normal bug, instead of one with a major effect on > usability. > > That said, if I have missed something that makes this a more major > problem (e.g., if it breaks some other tool in wheezy) then I'd be > happy to apply the fix.
I am not proficient with umask + setguid sticky, but Git doesn't respects whatever it was set in user session for sure. My specific case - when I mkdir in /var/www, the directory is created with group write permissions. When I git clone repository, the directory created by git doesn't have group write permission. This affects other users in my group who will try to `git pull` there. -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
