home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!sun-barr!sh.wide!wnoc-tyo-news!nec-tyo!nec-gw!mips!sdd.hp.com!ux1.cso.uiuc.edu!news.cso.uiuc.edu!murphy!fortony
- From: fortony@sonne.cso.uiuc.edu
- Subject: Re: Prevent user from editing /etc/passwd
- References: <1992Aug17.131329.22491@cpp.ob.open.de> <michaelv.714339575@test.cc.iastate.edu>
- Message-ID: <fortony.714343365@murphy>
- Originator: fortony@murphy
- Sender: usenet@news.cso.uiuc.edu (Net Noise owner)
- Organization: University of Illinois at Urbana
- Date: Thu, 20 Aug 1992 20:42:45 GMT
- Lines: 18
-
- schweik@cpp.ob.open.de (Martin Schweikert) writes:
-
- >Because I know he uses vi, I tried to replace /usr/bin/vi by a shell
- >script that tests if one of its parameters is *passwd. If so,
- >it would write a message to my terminal, send me mail, and make a copy
- >of /etc/passwd before it would invoke the original vi. Exactly here is
- >the problem: vi (I don't know much about it :-) seems to check under
- >what name it was invoked. And in my replacement script I invoked it
- >with "vi.orig". So vi finds out it wasn't invoked as vi, vedit, ... and
- >it seems that ex gets executed (I know perfectly nothing about ex).
-
- Why don't you just keep a copy of /etc/passwd around and periodically
- check for changes? If the extent of your mistrust of this person with
- root is high enough that you're scared of him, change his shell to
- /bin/goodnightirene and have him come talk it over with you in person.
- --
- a b c d e f g h i j k l m n o p q r s t u v w x y z
- Felix Sebastian Ortony fortony@murphy.gis.uiuc.edu
-