Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]

To: debian-user@lists.debian.org
Subject: Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
From: Sean 'Shaleh' Perry <shalehperry@attbi.com>
Date: Sat, 28 Sep 2002 01:14:53 -0700
Message-id: <[🔎] 200209280114.53030.shalehperry@attbi.com>
In-reply-to: <[🔎] 3D955DFA.8A76F2EB@iprimus.com.au>
References: <[🔎] 3D93582C.2090909@acu.edu> <[🔎] 20020928072722.GA13243@riva.ucam.org> <[🔎] 3D955DFA.8A76F2EB@iprimus.com.au>

On Saturday 28 September 2002 00:44, Russell wrote:
>
> Why is ./ in the path bad? If someone hacked in, couldn't they
> set the path to anything they wanted?

mostly because you just never know what you will find in '.'.  Being forced to 
type ./foo helps you be aware of where you are and what you are doing.

Reply to:

References:
- Odd Path issue
  - From: Kent West <westk@acu.edu>
- Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
  - From: Colin Watson <cjwatson@debian.org>
- Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
  - From: Russell <rjshaw@iprimus.com.au>

Prev by Date: Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
Next by Date: Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
Previous by thread: Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
Next by thread: Re: Dangerous to have ~/bin first in $PATH [was Re: Odd Path issue]
Index(es):
- Date
- Thread