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

2002-09-30 Thread Andy Saxena
On Sat, Sep 28, 2002 at 08:27:23AM +0100, Colin Watson wrote: > I disagree that this is a security risk. I want to override > system-provided executables, hence ~/bin is at the start of my $PATH. If > my user account gets hacked into, all bets are off; it's pointless to > worry about what somebody

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

2002-09-28 Thread Colin Watson
On Sat, Sep 28, 2002 at 05:44:58PM +1000, Russell wrote: > Colin Watson wrote: > > I think a more sensible rule is to only put directories in $PATH that > > are at least as trusted as the relevant account. Thus, /usr/bin and so > > on are always fine, ~/bin is only fine for the owning user, and .

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

2002-09-28 Thread Sean 'Shaleh' Perry
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 yo

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

2002-09-28 Thread Cameron Hutchison
Once upon a time Russell said... > Colin Watson wrote: > > > > I think a more sensible rule is to only put directories in $PATH that > > are at least as trusted as the relevant account. Thus, /usr/bin and so > > on are always fine, ~/bin is only fine for the owning user, and . is > > never a good

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

2002-09-28 Thread Russell
Colin Watson wrote: > > On Sat, Sep 28, 2002 at 03:15:42AM -0400, Andy Saxena wrote: > > On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > > > I'm using bash. "echo $PATH" reports: > > > > > > ~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games > > > > Putting ~/bin first in you

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

2002-09-28 Thread Colin Watson
On Sat, Sep 28, 2002 at 03:15:42AM -0400, Andy Saxena wrote: > On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > > I'm using bash. "echo $PATH" reports: > > > > ~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games > > Putting ~/bin first in your $PATH is a security risk. Conside

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

2002-09-27 Thread Kent West
Andy Saxena wrote: >On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > > >>I'm using bash. "echo $PATH" reports: >> >>~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games >> >> >> > >Putting ~/bin first in your $PATH is a security risk. Consider that if >your user account go

Re: Odd Path issue

2002-09-27 Thread Andy Saxena
On Thu, Sep 26, 2002 at 06:18:00PM -0700, Eric G. Miller wrote: > On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > > I'm using bash. "echo $PATH" reports: > > > > ~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games > > s/~/$HOME/ > > Guessing the ~ expansion in $PATH is a pro

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

2002-09-27 Thread Andy Saxena
On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > I'm using bash. "echo $PATH" reports: > > ~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games > Putting ~/bin first in your $PATH is a security risk. Consider that if your user account got hacked into, somebody could place a mo

Re: Odd Path issue

2002-09-26 Thread Kent West
Rich Rudnick wrote: >On Thu, 2002-09-26 at 12:09, nate wrote: > > > >>>KentTest", it reports the expected "/usr/local/bin/KentTest". However, >>>if I run "KentTest", I get "bash: /home/westk/bin/KentTest: No such file >>>or directory". If I log out and then log back in, I can run "KentTest" >>>

Re: Odd Path issue

2002-09-26 Thread Eric G. Miller
On Thu, Sep 26, 2002 at 01:55:40PM -0500, Kent West wrote: > I'm using bash. "echo $PATH" reports: > > ~/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games s/~/$HOME/ Guessing the ~ expansion in $PATH is a problem... -- begin 664 .signature M

Re: Odd Path issue

2002-09-26 Thread Vineet Kumar
* Kent West ([EMAIL PROTECTED]) [020926 12:00]: > I did a "chown +x test". From my home directory (/home/westk), I can run > "test" and I get no output. However, if I specify "bin/test", I get the > expect message ("This is a test"). If I do a "which test", it reports > "/home/westk/bin/test".

Re: Odd Path issue

2002-09-26 Thread Rich Rudnick
On Thu, 2002-09-26 at 12:09, nate wrote: > > > > > > KentTest", it reports the expected "/usr/local/bin/KentTest". However, > > if I run "KentTest", I get "bash: /home/westk/bin/KentTest: No such file > > or directory". If I log out and then log back in, I can run "KentTest" > > and it prints the

Re: Odd Path issue

2002-09-26 Thread nate
Kent West said: > I'm using bash. "echo $PATH" reports: > This is the first odd behaviour. test is also a shell command, which returns an exit value depending on what your testing for(see manpage on test). if your wanting to run it from your home I suggest ./test instead of just test that will t