Evan Van Dyke wrote:
Peter S Galbraith wrote:
If some user is capable of putting a fake `ls' in a random directory where
you might trip on it, that user is far more likely to put it in your ~/bin
directory! (Same privileges are required)
Just a thought.
Just make the . directory the
On Thu, 22 Oct 1998, Evan Van Dyke wrote:
Peter S Galbraith wrote:
If some user is capable of putting a fake `ls' in a random directory where
you might trip on it, that user is far more likely to put it in your ~/bin
directory! (Same privileges are required)
Just a thought.
Just
Helge Hafting wrote:
You don't have . in your path, so files are *not* considered executable
just because they are in the *current* directory.
This is a security feature. (Some user could make a nasty script called
ls or similiar in his home directoy. If you try to look at his
Grrr ...
I have a package of code which I want to compile using a supplied csh
script. I cannot get it to execute. The log reveals that it never
recognizes the script as a command. Of course, if I run it as
./compall rather than
compall
then commands found further in te script don't work
In [EMAIL PROTECTED], on 10/21/98
at 11:09 PM, [EMAIL PROTECTED] said:
Grrr ...
I have a package of code which I want to compile using a supplied csh
script. I cannot get it to execute. The log reveals that it never
recognizes the script as a command. Of course, if I run it as ./compall
[ script doesn't run because . not in path ]
Ways of solving the problem:
1. Create ~/bin and add that to your path. Put all private executables
in ~/bin You may want to set up you compiler to put freshly compiled
files there too. This works well and has no security problems.
Helge Hafting wrote:
You don't have . in your path, so files are *not* considered executable
just because they are in the *current* directory.
This is a security feature. (Some user could make a nasty script called
ls or similiar in his home directoy. If you try to look at his files
On Thu, 22 Oct 1998, Peter S Galbraith wrote:
:
: Helge Hafting wrote:
:
: You don't have . in your path, so files are *not* considered executable
: just because they are in the *current* directory.
:
: This is a security feature. (Some user could make a nasty script called
: ls
Peter S Galbraith wrote:
If some user is capable of putting a fake `ls' in a random directory where
you might trip on it, that user is far more likely to put it in your ~/bin
directory! (Same privileges are required)
Just a thought.
Just make the . directory the _last_ part of your path,
9 matches
Mail list logo
