Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!rutgers!mcnc!rock!mcmahan
From: mcmahan@cs.unca.edu (Scott McMahan)
Newsgroups: comp.unix.admin
Subject: Re: Mysterious security hole
Message-ID: <1991Jun22.220635.17145@rock.concert.net>
Date: 22 Jun 91 22:06:35 GMT
References: <52@bvnews1.bv.tek.com> <JC.91Jun21133441@raven.bu.edu> <1991Jun21.203054.989@serval.net.wsu.edu>
Sender: news@rock.concert.net
Organization: University of North Carolina at Asheville
Lines: 9

In article <1991Jun21.203054.989@serval.net.wsu.edu> yeidel@tomar.accs.wsu.edu (Joshua Yeidel) writes:
>>The example of having something in / is bad for obvious reasons.  But 
>>what about /tmp?  A script named say "la" (common type of "ls") which
>>does a chmod 777 /, sends mail to the person and then echos 
>>"la: Command not found" would do the job nicely. 
>
>Is /tmp in your path?  Why?

I wondered that myself.