🚀 go-pugleaf

In article <761nse$c7v$1@reader1.reader.news.ozemail.net>, Jason Stokes wrote:
>In article <MPG.10ee1412cad847ce989689@news.idx.com.au>, Paul Clyne
><pclyne@idx.com.au> wrote:
>
>>Hi, Me again...
>For security reasons Unix never executes a file in your current
>directory when you type an unqualified command, eg
>
> $ fortune
>
>The reason?  Someone on the machine might compile a trojan fortune
>program that does something nasty, put it in a directory with public
>read/execute permission, and every time someone strays in there and
>types that command the trojan fortune program executes instead of the
>real one.  To execute a program that isn't in your path, type the
>absolute or relative path before the program:


I agree 100% for a computer that has a public IP address, or has multiple
users that `.' should probably not be in the path at all.. but you give the
impression that the shell cannot be made to search the current directory.
This is rather easy to do.. but if it is done, it should be at the end.


One of the guys at Uni has modified bash to a paranoid shell that keeps
a database of the full path and timestamp of all applications that it
executes.. and you try to execute a program that has moved/changed or
is not in the search path it will apparently not execute unless you
prepend a special key word (riskit maybe).

http://www.cs.usyd.edu.au/~sholden/PASH


David Stanaway.