Quote:
Originally Posted by
sudon't
The thing that surprises me, is that bash says "command not found," when it had no trouble finding the file only a moment before.
The reason is that bash (and any other shell i know of) is bothering to even look in $PWD - unlike DOS/Windows, which did (and this way spoiled people). "bash" looks
exclusively along the PATH variable - and nowhere else. Whereas most application programs and system utilities default for
files to the PWD,
programs are only searched along the PATH. For this, if a program is not in a directory included in PATH, you have to use a complete path. This is either something like "/some/path/to/...." or "./path" - and "." is like a system variable meaning PWD.
Quote:
Originally Posted by
sudon't
If I may borrow from your example, someone who gained access to my account might look around and see the little innocuous scripts I'm writing, replace one of them with your malicious script, giving it the same name as one of mine.
True - but then the security-breach
has happened already by someone gaining access to your account.
bakunin