home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ferkel.ucsb.edu!ucsbcsl!fig!lsnyder
- From: lsnyder@fig.ucsb.edu (Lowell R. Snyder,,,COMS,Undergraduate)
- Newsgroups: comp.security.misc
- Subject: Re: Unix Viruses. Are there any??
- Message-ID: <7467@ucsbcsl.ucsb.edu>
- Date: 24 Jan 93 19:22:49 GMT
- References: <1993Jan15.090426.12195@unix.brighton.ac.uk> <17988@umd5.umd.edu> <senetza.727648754@honte>
- Sender: root@ucsbcsl.ucsb.edu
- Organization: University of California, Santa Barbara
- Lines: 17
-
- In article <senetza.727648754@honte> senetza@sigma.uleth.ca (Len Senetza) writes
- >so, if root executes your ls, then x is attached to some program in the
- >system. have your x only do it to programs which are suid. then it's
- >all over the place; memory protection and file access controls fail
- >here.
- >
- >this assumes that root has . in its path, and how many root accounts
- >out there do?
-
- Been there, done that. *Most* Unix sysadms have . as the last place to look
- for a file, with the system programmers (the ones that need it) using
- least privilege! This works around that problem.
-
- ------------------------------------------------------------------------------
- Try our new Eunichs - a slightly smaller version of the popular original,
- featuring the SpermControl Print Queue (the more copies you send, the more
- likely one will be printed).
-