If someone was able to access the box, create ~/bin and then drop a malicious script in there, then what would stop them from editing files that the user owns? Nothing.
It seems it's something specific to Debian, as a CentOS 5.5 box I have doesn't have anything like that in .bashrc. I can understand the convenience factor, if you place a different executable there, since it's first in $PATH, but if you are doing that, why not just edit $PATH manually? -- You received this bug notification because you are a member of Registry Administrators, which is the registrant for Debian. https://bugs.launchpad.net/bugs/684393 Title: $PATH discrepency when ~/bin exists _______________________________________________ Mailing list: https://launchpad.net/~registry Post to : registry@lists.launchpad.net Unsubscribe : https://launchpad.net/~registry More help : https://help.launchpad.net/ListHelp
