On Mon, Feb 14, 2005 at 08:53:28PM -0600, Analabha Roy wrote: | > > I use sudo to execute the scripts I wrote to manage my wireless | > > connection. :P ... | Is that a good idea? I mean, sudo means that anybody in the sudoers list | can execute ur script with root privs w/out the root passwd, is that | wise?
That is exactly what sudo is for. As for it being wise, that depends on what programs you allow access to. You may let your wife use your computer, but don't want to give her root access to shut it down. So instead you set up sudo to let her execute shutdown (as root) so she can shut it down. The danger there is that now your wife can shut down your computer, and may not realize that you're logged in remotely. | Why not use kdesu instead? Just add a line "kdesu -c "/path-to-script" | and all u have to do is enter the root password when the GUI prompt | shows up. kdesu is just a GUI for /bin/su. Nothing more. sudo allows a user, who probably does not know the root password, to run a program that you have set up beforehand as root. Setting up the wireless stuff is a fine example of a task that requires root that you might want somebody else to have access to. | It's what I do, I'm just not too comfortable with sudo. In fact, the | only file that I have sudoed is the "su" binary itself (can't do | without THAT, heh). If you're the only one who ever uses your computer, and you know the root password, there's little need for sudo (though you could still set it up so that certain things that require root can be done by you without su'ing to root.) It's quite useful when multiple people use a box, and all need some access to root (usually to run a few specific programs or scripts) but you don't want to give everybody full root access. -- Doug McLaren, [EMAIL PROTECTED] Vote anarchist! _______________________________________________ Siglinux mailing list Siglinux@utacm.org http://www.utacm.org:81/mailman/listinfo/siglinux
