home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!sdd.hp.com!cs.utexas.edu!hellgate.utah.edu!lanl!beta.lanl.gov!jfowler
- From: jfowler@beta.lanl.gov (John C. Fowler)
- Newsgroups: comp.security.misc
- Subject: Re: Re: root-owned world-writable files
- Message-ID: <1992Jul23.141105.27963@newshost.lanl.gov>
- Date: 23 Jul 92 14:11:05 GMT
- References: <1992Jul21.201056.662@newshost.lanl.gov> <61350001@otter.hpl.hp.com>
- Sender: news@newshost.lanl.gov
- Organization: Los Alamos National Laboratory
- Lines: 14
-
- In article <61350001@otter.hpl.hp.com> sjmz@otter.hpl.hp.com (Stefek Zaba) writes:
- >For example: a wannabe sysadmin leaves their home directory world-writeable.
- >This allows the attacker to plant a .rhosts file which will allow them in.
-
- And if there are no root-owned world-writable files, then the attacker could
- mv the old /etc directory out of the way, mkdir a new /etc directory, copy
- the appropriate files, and change root's password in /etc/passwd. Or maybe
- they'll just delete the kernel (any system administrator dumb enough to
- leave / world-writable is not likely to know how to recover).
-
- But I see the point you're trying to make. Thanks for bringing it up!
-
- --
- John C. Fowler, jfowler@lanl.gov
-