Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!nrl-cmf!cmcl2!brl-adm!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!uiucdcs!uxc.cso.uiuc.edu!ccvaxa!aglew
From: aglew@ccvaxa.UUCP
Newsgroups: comp.arch
Subject: Re: ITS translations: security prob
Message-ID: <28200096@ccvaxa>
Date: 9 Feb 88 01:15:00 GMT
References: <1515@osiris.UUCP>
Lines: 18
Nf-ID: #R:osiris.UUCP:1515:ccvaxa:28200096:000:747
Nf-From: ccvaxa.UUCP!aglew    Feb  8 19:15:00 1988


>>In article <9690@tekecs.TEK.COM> andrew@frip.gwd.tek.com (Andrew Klossner) writes:
>>	  So you add s|^/bin/rm$|/user/me/bin/rm| to your
>>	translation list."
>>
>
>	Rather than building things like this into the OS, they can just as
>easily be handled in the shell. Rather than forcing everyone to worry about
>security problems, etc, etc, why not simply have your shell support all the
>translation you can handle, since the UNIX file system layout is pretty
>straightforward.
>
>--mjr();

I am sure that mjr is aware of the obvious deficiency of shell only 
translations: execl("/bin/cp",...).

The shell is not the place to put all extensions. Witness how RMS is trying
to get POSIX to phrase file name semantics so that ~ can be put in GNU.