mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: June 20 2007,19:40 |
 |
Quote | DSL boots by default to user dsl with sudo privileges but not direct root privileges. This is the proper, more secure way of running a Unix/Linux environment. | While I agree with your post as a whole, this one comment is something I don't fully agree with. It's my personal belief that the "proper" way to do it would be to require a root password for *any* root access. DSL makes it a little too easy for my own taste. I've made it a point to create both a dsl and root password, but still have not fully addressed this aspect of security to my liking. At some point I'll either modify sudoers (which is still a very confusing topic for me) or create a replacement script for the sudo command on top of my PATH (e.g., running "su -c $@" whenever sudo is called). For now, though, I have no idea how complicated it might be for applications like mydsl, which run in X but spawn scripts that use sudo, and haven't had the desire to experiment with it yet.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|