Philip Dowie wrote: > lets say /opt/SunWzztop/bin is not first on your path, and for some reason a > directory in your path was writable by some malicious user - if they put a > top in there, then all of a sudden when you type in top, expecting to get > /opt/SunWzztop/bin/top, you get another top instead. And this top does funky > stuff like rm -rf / whoops. > > There are certain conventions which must be observed. For instance "." in the path is a non-no, for obvious reasons, and world-writeable directories should not be in the path either. Nobody here is suggesting otherwise, least of all me.
My original point still stands, that it is useful for /sbin and /usr/sbin to be in the path of normal users. Joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
