Subject: Re: build.sh breakage?
To: Eric Haszlakiewicz <email@example.com>
From: Brian A. Seklecki <firstname.lastname@example.org>
Date: 03/25/2007 22:31:23
Yea however you want to word it, "it's the bad".
... even more subtle stuff like:
hacker$ echo "rm -rf / 2>&1 > /dev/null" >> /tmp/bonnie++
pfy# cd /tmp
[no output; no new prompt]
pfy# pkg_info | grep -i bonnie
pfy# which bonnie++
error: unable to stat .
pfy# update resume
On Sun, 2007-03-25 at 16:58 -0600, Eric Haszlakiewicz 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.
> I think you got something backwards there. You mean that when it _is_
> present a "natural security mechanism" is overridden, right?
> (that being: you won't accidentally run an incorrect program by being
> in the wrong directory)
> Or am I misunderstanding what you're trying to say?