On Thursday 18 July 2002 11:06 am, Brian T. Schellenberger wrote:
| IMHO, "op" is far superior to "sudo."
Hmm . . . come to think of it, that's a little terse.
"op" is easy to configure, and it allows you give access to people not to
certain commands but to certain commands *only* with certain parameters.
It has lots flexibility in specifying which commands and which groups of
people and so forth. Also whether to prompt for passwords or not with equal
flexibility.
It's also less syntactically painful when the user uses it.
In spite of all this, the access-control file is quite simple to work with.
|
| On Wednesday 17 July 2002 03:04 pm, Tom Limoncelli wrote:
| | "Balaji, Pavan" wrote:
| | > I wonder what exactly this means. I don't remember seeing any option
| | > for creating/not-creating the wheel group while installation.
| |
| | It means "Install 'sudo' so that you get tighter control over who can do
| | what, and much better logging."
| |
| | :-)
| |
| | I've known about sudo for ages but only started using it. After learning
| | the configuration syntax, I've found it a great little utility. There
| | are now many cases where I used to hand out root access but now I only
| | have to give sudo access to a particular command. (Disclaimer: you
| | shouldn't give sudo access to any command that you haven't personally
| | audited or you may be giving the person full root access without knowing
| | it.)
| |
| | --tal
--
Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal)
http://www.babbleon.org
http://www.eff.org http://www.programming-freedom.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
