Linked by Thom Holwerda on Tue 20th Dec 2011 22:01 UTC, submitted by RichterKuato
Permalink for comment 500827
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
More News »
Sponsored Links



Member since:
2006-01-14
If you are in a *nix group that enables you to su to root or run sudo...and, you don't want to be limited to installing apps in your home directory....and, you don't want to be prompted to enter a password.....then, I see 1 option: log in as root.
Otherwise, how would your OS know that it is OK for you to install applications system wide to directories like /bin and /sbin, but not execute privileged commands like rm -fr /bin and rm -fr /sbin?
I'm not an expert in *nix security. I've always just accepted things for being the way they are because I give the benefit of the doubt to the kernel hackers. I trust it's all been well thought out. If you really want less security, run it less securely or run a less secure OS. Problem solved.