![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| Linux RedHat, Ubuntu, SUSE, Fedora, Debian, Mandriva, Slackware, Gentoo linux, PCLinuxOS. All Linux questions here! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| sudo question | melias | Security | 12 | 05-26-2008 01:10 AM |
| sudo, or not sudo: that is the question | iBot | UNIX and Linux RSS News | 1 | 02-07-2008 10:40 AM |
| Sudo question | Zarnick | Linux | 2 | 01-22-2008 05:25 AM |
| SUDO question - please help | sajjad02 | UNIX for Advanced & Expert Users | 5 | 04-27-2005 08:22 AM |
| sudo question | TRUEST | UNIX for Dummies Questions & Answers | 1 | 01-16-2004 09:53 PM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#8
|
|||
|
|||
|
If your senior programmer doesn't know much about systems and he has the root password, I suggest you use the command passwd to change the root password.
Then, set up sudo for that user so they have a list of defined commands they can execute as a super user. else, I suggest that you alias the command su to something else that echos a warning to the user. then run the su command as a different name. You NEVER want to re-engineer security around a user who should not have privileges in the first place. Root is not "the boss" he is god on that machine. He can instruct the machine to destroy itself (software wise). Cleaning up those messes will not be fun. |
|||
| Google The UNIX and Linux Forums |
| Forum Sponsor | ||
|
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|