Xref: utzoo comp.unix.wizards:6421 comp.arch:3337
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!mimsy!aplcen!osiris!mjr
From: mjr@osiris.UUCP (Marcus J. Ranum)
Newsgroups: comp.unix.wizards,comp.arch
Subject: Re: ITS translations: security problem?
Message-ID: <1515@osiris.UUCP>
Date: 5 Feb 88 14:30:07 GMT
References: <1495@osiris.UUCP: <2126@haddock.ISC.COM> <1497@osiris.UUCP> <704@PT.CS.CMU.EDU> <1424@gumby.mips.COM> <9690@tekecs.TEK.COM> <16008@think.UUCP>
Reply-To: mjr@osiris.UUCP (Marcus J. Ranum)
Organization: Institute For Felinographical Studies
Lines: 25

>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.
	
	Sure, there'd be a performance hit, but it's better to keep those
in the shell, and keep everything else as straightforward as possible.
Golly, I can see it now:
s/\/usr\//C:/g
s/\/$HOME\/D:/g
...


--mjr();

-- 
------------------------------------------------------------------------------
...ich bin in einem dusenjet ins jahr 53 vor chr...ich lande im antiken Rom...
                     einige gladiatoren spielen scrabble...ich rieche PIZZA...