From:	fcusack AT iconnet DOT net (Frank Cusack)
Subject:	Re: cygwin b20 bash path usage?
13 Nov 1998 06:39:43 -0800 :
Message-ID:	<199811122221.RAA20342.cygnus.gnu-win32@ratbert.iconnet.net>
References:	<od1zn9d9as DOT fsf AT northpole DOT cygnus DOT com>
To:	Eric Christopher <echristo AT cygnus DOT com>
Cc:	gnu-win32 AT cygnus DOT com

In message <od1zn9d9as DOT fsf AT northpole DOT cygnus DOT com>, 
Eric Christopher writes:
> vos AT channelpoint DOT com (Craig Vosburgh) writes:
> 
> > bash will use the PATH variable to determine the search order.  It
> > sounds like you need to put . in your PATH variable first or execute the
> > test command as ./test.  If you have any question which executable is
> > being executed you can always use the type command to see what bash hash
> > hashed for that name (e.g. type test should return the path to the test
> > executable being executed)
> 
> '.' should always be put last in your path.  It is a horrible security hole
> if you do otherwise.
> 

Even last it's a big hole. [Think: common typos]

~frank

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -