home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!wupost!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!ge-dab!puma.ATL.GE.COM!rsnyder
- From: rsnyder@atl.ge.com (Bob Snyder)
- Newsgroups: comp.unix.admin
- Subject: Re: Prevent user from editing /etc/passwd
- Message-ID: <1992Aug30.233345.13354@puma.ATL.GE.COM>
- Date: 30 Aug 92 23:33:45 GMT
- References: <1992Aug20.165851.13565@csus.edu> <1992Aug24.172610.15580@cc.ic.ac.uk>
- Sender: news@puma.ATL.GE.COM (USENET News System)
- Organization: GE Aerospace, Advanced Technology Labs
- Lines: 20
-
- In article <1992Aug24.172610.15580@cc.ic.ac.uk> cmaae47@cc.ic.ac.uk writes:
-
- >cp /obscure/etc/passwd /etc/passwd
- >
- >as part of the boot-up sequence, so that if somebody reconfigures the system
- >incompetently (i.e. without reading the instructions on how to do the
- >obscurated files) just rebooting will fix it again.
- >
- >The actual trigger event could be anything, even a cron job running every 5
- >seconds, and the copying could be done via cpio to copy the whole obscure
- >tree to /.
-
- This, of course, is rather painful if you decide to allow users to change
- their password, shell, or user name.
-
- Bob
-
- --
- Bob Snyder, Computing Services, GE Aerospace, Advanced Technology Labs
- rsnyder@atl.ge.com, (609) 866-6672, FAX: (609) 866-6397, DialComm 8*777-6672
-