Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!mcsun!ukc!stc!miclon!ibmpcug!dylan
From: dylan@ibmpcug.co.uk (Matthew Farwell)
Newsgroups: comp.unix.questions
Subject: Re: How to prevent VI from getting a shell?
Message-ID: <1990Sep18.071435.6357@ibmpcug.co.uk>
Date: 18 Sep 90 07:14:35 GMT
References: <501@trux.UUCP> <570@DIALix.UUCP> <1990Sep17.210110.26060@robobar.co.uk>
Reply-To: dylan@ibmpcug.CO.UK (Matthew Farwell)
Organization: The IBM PC User Group, UK.
Lines: 24

In article <1990Sep17.210110.26060@robobar.co.uk> ronald@robobar.co.uk (Ronald S H Khoo) writes:
>In article <570@DIALix.UUCP> bernie@DIALix.oz.au (Bernd Felsche) writes:
>> set SHELL in the environment to something which doest nothing, say
>> /bin/true.  vi forks-execs whatever SHELL is defined to be, or the
>> shell if undefined.
>I don't know about *your* version of vi, but mine lets you defeat this
>by doing :set shell=/bin/sh
>I got around the problem by binary patching out the call to fork() in
>vi.  Ugh.  Also, I never found a way to defeat letting the user read and
>write files other than the current file.  Any offers ?

#ifdef PLUG_ELVIS
You install elvis, like I will when I get around to it + people who
know how to break vi have a go at breaking it. (subtle hint ron).

Elvis is nice + easy to disable commands. I actually quite like it.
#endif

Dylan.
-- 
Matthew J Farwell                 | Email: dylan@ibmpcug.co.uk
The IBM PC User Group, PO Box 360,|        ...!uunet!ukc!ibmpcug!dylan
Harrow HA1 4LQ England            | CONNECT - Usenet Access in the UK!!
Phone: +44 81-863-1191            | Sun? Don't they make coffee machines?