home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!nwnexus!Celestial.COM!camco!soundex.Celestial.COM!stephsf.com!kopachuk!dcb
- From: dcb@kopachuk.uucp (David Breneman)
- Subject: Re: Prevent user from editing /etc/passwd
- Message-ID: <1992Aug25.160144.1531@kopachuk.uucp>
- Organization: Tacoma Screw Products, Inc.
- References: <1992Aug17.131329.22491@cpp.ob.open.de> <21390@rpp386.lonestar.org> <170j07INNoj3@early-bird.think.com>
- Date: Tue, 25 Aug 1992 16:01:44 GMT
- Lines: 21
-
- In article <170j07INNoj3@early-bird.think.com> barmar@think.com (Barry Margolin) writes:
- >In article <21390@rpp386.lonestar.org> jfh@rpp386.cactus.org (John F. Haugh II) writes:
- >
- >The question I have is why would someone who can't be trusted not to edit
- >the passwd file be authorized to have the root password. If he needs to be
- >able to do a few things that require superuser access, maybe you need
- >something like "sudo", which permits you to give him a specific set of
- >commands that run with root privileges.
- >
- Well, in a family-owned company for instance, a member of the owner's
- family may insist that he/she "needs" root access just because that
- person doesn't like the idea of an "outsider" having more priviledge
- than themself (mind you, this is a hypothetical situation ;-) ).
- In such a case, you run the real risk of having a dilettante screw
- things up massively. BTW, what is "sudo"?
-
- --
- David Breneman Sys Admin, Tacoma Screw Products, Inc. | ____ ____ ____
- dcb@tacoma.uucp | SCREWIE the TSP CLOWN sez- | / /___ /___/
- ..!uunet!tacoma!dcb | "Nylok lock nuts lose their | / ____/ /
- CompuServe: 75760,1232 | binding strength after 1 use!"|
-