evaluatesecuritymeasures
In Linux the security often seems to get in the way...yet we don't want to get rid of it. How about evaluating default policies and reconfiguring the system. For example, an enormous time-drain on the forums is composed of the requests of users concerning why they can't access their own partitions' contents...which turn out to be Fat32 mounted partitions which, since that filesystem doesn't support the same security featues as others, gets mounted very under the utmost restrictive permissions and as owned by root; how about setting this to owned by the user on mount?
There are other things like permissions policies which end up causing "bugs"; one such bug is that trying to empty the trash is suddenly blocked because the users "does not have permissions"; maybe this is more related to the aforementioned gaff...but other security measures might create similar issues. Let's get brains churning to correct such flaws...without lowering security standards. : )
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by