Date: Sat, 09 Jan 1999 23:03:00 -0700 From: Warner Losh <imp@village.org> To: Stephen McKay <syssgm@dtir.qld.gov.au> Cc: Steve Kargl <sgk@troutmask.apl.washington.edu>, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/gnu/usr.bin/binutils/strip Makefile Message-ID: <199901100603.XAA08530@harmony.village.org> In-Reply-To: Your message of "Sun, 10 Jan 1999 00:15:24 %2B1000." <199901091415.AAA23180@nymph.dtir.qld.gov.au> References: <199901091415.AAA23180@nymph.dtir.qld.gov.au> <199901081728.JAA91509@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199901091415.AAA23180@nymph.dtir.qld.gov.au> Stephen McKay writes:
: Yes, "." in $PATH is bad and can be dealt with by aborting (or editting it
: out) but if you think malicious users have fiddled with your makefiles,
: you've got bigger problems than your $PATH!
If they can fiddle with the makefiles, they can fiddle with the
source, . or no in your $PATH.
There is nothing wrong with having . in your path[*], but if it causes
builds to fail, why not filter it in the make {,build,install}world
targets?
Warner
[*] At the end of the $PATH, and only when you aren't root.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901100603.XAA08530>