Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!newsroom.utas.edu.au!munnari.OZ.AU!spool.mu.edu!torn!news.bc.net!rover.ucs.ualberta.ca!atha!sgiblab!sgigate.sgi.com!swrinde!newsfeed.internetmci.com!in1.uu.net!hearst.acc.Virginia.EDU!maui.cc.odu.edu!news From: Ragnar <bowden@cs.odu.edu> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: compiled program won't run. Date: Fri, 17 Nov 1995 12:58:40 -0500 (EST) Organization: Old Dominion University Lines: 17 Message-ID: <Pine.SUN.3.90.951117125554.19452B-100000@hurricane.cs.odu.edu> References: <480g7u$t2e@news.csus.edu> <dhawkDHvzsq.F5r@netcom.com> NNTP-Posting-Host: hurricane.cs.odu.edu Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <dhawkDHvzsq.F5r@netcom.com> On Sat, 11 Nov 1995, David H wrote: > If security is not a concern, set path = ( $path . ) > as root to add the current directory to its path and if you > install a binary somewhere type rehash Would someone please explain why having a . in your path is a security issue? I have heard this since I started using unix, but I find it difficult to believe or justify. If /usr/local/bin is in my path, and i happen to be in /usr/local/bin, then effectively, the . (read current) directory is in my path. What gives? Jamie If Zeno's paradox is true, then how did he get halfway there in the first place?