🚀 go-pugleaf

rickert@mp.cs.niu.edu (Neil Rickert) writes:

>In article <67@nearside.UUCP> shwake@nearside.UUCP (Raymond Shwake) writes:
>>dkeisen@leland.Stanford.EDU (Dave Eisen) writes:
>>
>>	I like to set SHELL to /bin/echo; the only point is to invoke
>>	something innocuous.
>>
>>>This doesn't do any good. The user can still type :set shell=/bin/csh
>>>and give himself a shell whenver he wants. The SHELL environment
>>>vaiable is only used to initialize the internal vi shell variable.
>>
>>	Quite true. What I've done is binary patch the "set" string to
>>	include an embedded space (like "s x"). Seems to work.

>Try doing

>	:r !command

>chances are you find that still uses /bin/sh, regardless of your SHELL
>environment.

Listen guys, get elvis (from GNU) or xvi (from SIMTEL::msdos/editors -
a not too bad windowed vi for char terminals), and remove the offending
code, compile and use this.  Then make the REAL vi executable only by
appropriate people.

I did a similar job on kermit, removing ability to delete files, etc, etc
, etc - took a couple of hours.

This is why having sources is so damn handy ?


David T. Bath	Email:dtb@otto.bf.rmit.oz.au	Phone:03-3477511
Global Technology Corporation, 179 Grattan St, CARLTON, VIC, 3153, AUSTRALIA
"Failure to emulate is the best revenge" - Marcus Aurelius

-- 
David T. Bath	Email:dtb@otto.bf.rmit.oz.au	Phone:03-3477511
Global Technology Corporation, 179 Grattan St, CARLTON, VIC, 3153, AUSTRALIA
"Failure to emulate is the best revenge" - Marcus Aurelius