Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!henry
From: henry@utzoo.UUCP (Henry Spencer)
Newsgroups: net.unix-wizards
Subject: Re: Please do NOT use "/bin/test" as a command name
Message-ID: <6223@utzoo.UUCP>
Date: Thu, 12-Dec-85 16:47:39 EST
Article-I.D.: utzoo.6223
Posted: Thu Dec 12 16:47:39 1985
Date-Received: Thu, 12-Dec-85 16:47:39 EST
References: <313@bdaemon.UUCP> <13400016@mirror.UUCP> <1016@sdcsla.UUCP>
Organization: U of Toronto Zoology
Lines: 11

> 	Also, I would love to try to break into a system kept secure by your
> shell scripts which do not contain absolute path names.  I would do exactly
> what you suggest - substitute my own versions of rm, mv, etc...

Wouldn't help, since all those shell scripts start with the magic line:

	PATH=/bin:/usr/bin ; export PATH

which solves the problem without requiring hardwired path names everywhere.
Also, it solves the problem for everything invoked by the shell script,
rather than just for the shell script itself.