Improve customizability for UMASK and default permissions #36367
Labels
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
enhancement
feature: filesystem
How to use GitHub
Improve customizability for UMASK and default permissions
Respect user
$UMASK
andfacl
while ensuring NC can write & manage the folders it creates e5dc1a8.Possible Solution 0
Stop playing with permissions.
Add checks in the " Security & setup warnings " section for FS configuration.
Then, in normal workflow, report any FS errors to both admin and users.
Possible Solution 1
If we have to play with permissions, instead of overriding
$UMASK
before creating the file and forcing a defaultchmod
:$MIN_PERM_F
and$MIN_PERM_D
instead of hardcoding (we may want NC to rely on the user or the group or on all)...Bonus
Since we are manipulating the permissions anyway, we may want to try playing nice with NFS & friends:
chown
the file uploaded by that user asuser_uid:oc_gid
facl
ACLs
This, combined with
inotify
support (which NC kinda has-- INotify file watcher ) for change detection, would be magic.The flexibility and ease of use of Nextcloud while accessing remotely.
The performance of NFS when needed.
Context
Deprecates: #29041 #25280
Builds upon: #32723 (merge&shipped NC 25)
The text was updated successfully, but these errors were encountered: