Subject: Re: build.sh breakage?
To: David Laight <email@example.com>
From: Brian A. Seklecki <firstname.lastname@example.org>
Date: 03/25/2007 22:33:25
There's always the possibility you're $PWD is a og+w bit
(/tmp, /var/tmp) and someone slips in an executable shell script there
for a command you might type that isn't located in $PATH yet.
On Sun, 2007-03-25 at 20:22 +0100, David Laight wrote:
> On Sun, Mar 25, 2007 at 12:36:22PM -0500, Brian A. Seklecki wrote:
> > > /home/paul/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/X11R6/bin:\
> > > /usr/pkg/bin:/usr/pkg/sbin:/usr/games:/usr/local/bin: \
> > > /usr/local/sbin:.
> > I once had my life (well, life of my livelihood) threatened by a
> > very .....imposing (politically correct) female system administrator for
> > putting "." in my $PATH.
> > It not being present overrides one of the natural security mechanisms
> > present in UNIX-like environments.
> Actually it usually does no harm as the last item, and the scripts
> shouldn't barf at that.
> They can also report the actual item causing grief.