Xref: utzoo alt.security:1625 alt.bbs:3034 comp.unix.sysv386:731
Path: utzoo!utgpu!cs.utexas.edu!uunet!van-bc!rsoft!frank
From: frank@rsoft.bc.ca (Frank I. Reiter)
Newsgroups: alt.security,alt.bbs,comp.unix.sysv386
Subject: Re: Protecting against downloads
Message-ID: <93@rsoft.bc.ca>
Date: 25 Sep 90 20:24:29 GMT
References: <2441@sud509.ed.ray.com> <1990S <1990Sep20.153105.28394@naitc.naitc.com> <1990Sep22.024446.3305@chinet.chi.il.us> <1990Sep24.153529.8627@naitc.naitc.com> <1990Sep25.122420.9231@ibmpcug.co.uk>
Reply-To: frank@rsoft.UUCP (Frank I. Reiter)
Organization: Reiter Software Inc., British Columbia
Lines: 18

In article <1990Sep25.122420.9231@ibmpcug.co.uk> dylan@ibmpcug.CO.UK (Matthew Farwell) writes:
>
>I agree that it is actually a feature.  Its a pain when you need to
>actually take the shell escapes out, but thats true of every editor when
>you haven't got the source.  Look at emacs.  How would you restrict that
>if you didn't have the source?  (how could you restrict emacs anyway???)
>Its not a bug.  Its a feature.

Pity there isn't a simple -R (restricted) flag that could be given on the 
command line.  This could prevent shell escapes, and perhaps prevent reading
or writing files outside of the current directory.


-- 
_____________________________________________________________________________
Frank I. Reiter              UUCP:  {uunet,ubc-cs}!van-bc!rsoft!frank
Reiter Software Inc.                frank@rsoft.bc.ca,  a2@mindlink.UUCP
Surrey, British Columbia      BBS:  Mind Link @ (604)576-1214, login as Guest