On Thu, Feb 23, 2017 at 8:03 PM, Branko Čibej <br...@apache.org> wrote:
> No. They're granted whatever access is allowed by the umask. See > https://en.wikipedia.org/wiki/Umask > > If the umask is 002 then all created files will, by default, allow read > and write access to the user and the user's primary group. Neither > Subversion nor SQLite tries to be smart in any way in this respect. > > There are other ways to control permissions on new files: your > filesystem could have inheritable ACLs that prevent group-write > permission to be granted, regardless of umask. Your SELinux > configuration could do that, too. > > In any case, this is not a Subversion bug. > > -- Brane SELinux, perhaps? Check "/etc/sysconfig/selinux" and prepare to reset it to "warning" mode, and check the logs for SELinux errors? And there are other compelling reasons to avoid putting shared workspaces in individual user home directories.
