ClearFoundation Tracker - ClearOS | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0014021 | ClearOS | app-flexshare - Flexshares | public | 2017-03-24 12:37 | 2017-03-28 09:37 |
Reporter | user2 | ||||
Assigned To | user2 | ||||
Priority | normal | Severity | tweak | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Platform | OS | OS Version | |||
Product Version | 7.3.1 | ||||
Target Version | 7.3.1 Updates | Fixed in Version | 7.3.1 Updates | ||
Summary | 0014021: Change file/folder permission handling | ||||
Description | From experience, we have seen Flexshare permissions get out of whack from: - Using scp or other tools to drop files into a Flexshare - Some Windows programs changing permissions on save (instead of using the existing permissions). - End-users messing around with ACLs For this reason, a daily Flexshare cronjob comes along and fixes these issues. Thankfully, we don't get that steady stream of "broken file share permission" support tickets these days. However, web server document roots also fall under this file/folder permission cronjob. Web server document roots often need specialized permissions, so we should avoid running the permissions fix on this type of Flexshare. If a user wants to enforce permissions across all Flexshare types, change the following flexshare.conf parameter to "full": FlexshareSecurityPermissions=full (default is FlexshareSecurityPermissions=on) | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2017-03-24 12:37 | user2 | New Issue | |||
2017-03-24 12:37 | user2 | Status | new => resolved | ||
2017-03-24 12:37 | user2 | Fixed in Version | => 7.3.1 Updates | ||
2017-03-24 12:37 | user2 | Resolution | open => fixed | ||
2017-03-24 12:37 | user2 | Assigned To | => user2 | ||
2017-03-28 09:37 | user2 | Status | resolved => closed |
There are no notes attached to this issue. |