Robert Citek wrote:
As for security, if someone is putting or modifying executable code in your ~/bin, then I would not worry about where ~/bin appears in your PATH.
I had thought about security in my earlier post. And I concur that you probably have bigger problems if someone can access any part of your home directory. The same thing is true for the infamous "." in your path. Modern shells require the "./myscript.sh" before they will run.
I run a find script to show the last modified time of all files/dirs. Come to think of it, maybe that should be run in every .login and compare things like last login dates etc.
Maybe Robert is right and we should not have ~/bin at all (or in your PATH) and alias explicit paths. Harder to set them up but maybe more effective, and with that much RAM who cares. (I have an alias that saves all my aliases to a startup file.)
Did anyone right the book "Highly effective Security Measures of the Successful End User" yet?
Ed
-- Ed Howland WDT Solutions, LLC. [EMAIL PROTECTED] (314) 962-0766
_______________________________________________
CWE-LUG mailing list
http://www.cwelug.org/ [email protected]
http://lists.firepipe.net/listinfo/cwe-lug
