The big question and TLDR: What is changing the permissions on my owncloud_data folder and how can I keep those permissions from changing?
I do not think this is a “bug” but rather just a setting I am unaware of. I believe I have provided the necessary information below. Thank you in advance
My organization would like to leverage Symantec DLP to ensure no sensitive information is being stored and shared within our Owncloud data. Our proposed way of accomplishing this is to setup a NFS share from the Linux gluster server and mount it on the Windows Symantec DLP machine. The owncloud data folder is on a mount point aka /mnt/OwnCloud_Data
On the Gluster server the current permissions of the Owncloud data folder are 770 and the ownership is user 48 group 48.
If I change the permissions on the folder to 775 (yes, I know this is relatively insecure but absolutely no one has access to the gluster server except administrators) I can successfully mount the folder and view the contents in windows. Keeping in mind that access to the NFS share is restricted to explicitly defined IP addresses.
My issue is the permissions on the Owncloud data folder keep automatically reverting back to 770, which breaks the ability to view the files and I am unsure why the permissions are reverting.
Windows 10 NFS client
Gluster server and Apache (WWW) server are separate. No user with UID or GUID 48 exists on Gluster server but this matches the UID and GUID of the apache user on the WWW server which has ownership of these files. These servers are in production and I do not have a lower environment to test on and am wary of changing any of the ownership or adding new users/groups. I would rather expand permissions to Other than modify any of the existing User/Group.
I have attempted to do things such as change the anonymousUID/GUID in my windows registry to be “48” but that did not allow me to view the files.