Date: Mon, 25 Jun 2001 10:29:18 +0200 From: Leon Breedt <ljb@devco.net> To: Ted Mittelstaedt <tedm@toybox.placo.com> Cc: freebsd-security@FreeBSD.ORG Subject: Re: Kernel Panic Message-ID: <20010625102918.A268@rinoa.prv.dev.itouchnet.net> In-Reply-To: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> References: <200106221156.AA442106040@stmail.pace.edu> <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 24, 2001 at 02:01:34AM -0700, Ted Mittelstaedt wrote:
> That would be impossible unless you had "." in your path. If
> you did (which is a very BAD thing) then yes your script probably
> loaded itself (assuming you named it "pine). This is why the
> system defaults to NOT having "." in the path.
I'm not sure if everyone's aware of this (I wasn't), but an
empty colon in your PATH is an implicit . (!!)
i.e. PATH=/bin:/usr/bin:/usr/local/bin:
In sh(1):
2. The shell searches each entry in PATH in turn for the command. The
value of the PATH variable should be a series of entries separated
by colons. Each entry consists of a directory name. The current
directory may be indicated implicitly by an empty directory name, or
explicitly by a single period.
Regards,
Leon.
--
lj breedt
coder
"Threads are for people who can't program state machines."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010625102918.A268>