Timeline for Why is root security enforced but $HOME typically unprotected?
Current License: CC BY-SA 3.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 9, 2018 at 3:33 | comment | added | millebi | @AndrolGenhald many applications supply helper scripts that set "stupid" permissions (e.g. 700) which then make the files unreadable by other users. It's stupid, I agree, but I've seen it happen too many times to count. forest I agree! Some SA's change the default on secure systems to a different umask :( which usually bites them later. (Stupidity is billable) | |
Mar 2, 2018 at 23:33 | comment | added | forest |
Anyone who runs rm -rf with a * anywhere in the argv deserves to lose their data. And @AndrolGenhald is right. Usually root-owned files are readable if created with a umask of 022 (the default). Btw, set -u is a thing. Use it.
|
|
Mar 2, 2018 at 17:49 | comment | added | AndrolGenhald |
"because many activities will change the ownership of files to become root...applications...can't read the default configuration" - Such as? /etc is world-readable by default.
|
|
Mar 2, 2018 at 17:44 | review | First posts | |||
Mar 2, 2018 at 17:52 | |||||
Mar 2, 2018 at 17:43 | history | answered | millebi | CC BY-SA 3.0 |