Xref: utzoo alt.security:1610 comp.unix.sysv386:650
Path: utzoo!attcan!utgpu!cs.utexas.edu!yale!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: alt.security,comp.unix.sysv386
Subject: Re: Here's how to stop shell escapes from vi
Message-ID: <27387:Sep2320:07:3890@kramden.acf.nyu.edu>
Date: 23 Sep 90 20:07:38 GMT
References: <1990Sep20.153105.28394@naitc.naitc.com> <11285:Sep2022:15:2090@kr <924@mwtech.UUCP>
Organization: IR
Lines: 15

In article <924@mwtech.UUCP> martin@mwtech.UUCP (Martin Weitzel) writes:
> In article <11285:Sep2022:15:2090@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> > In article <1990Sep20.153105.28394@naitc.naitc.com> karl@bbs.naitc.com (Karl Denninger) writes:
     [ that as long as : is available, you can get a shell ]
> > >Without source code to "vi" there is NO WAY to prevent this.  Believe me.  
> > How fatalistic.
    [ trash the colon with pty -0 tr \: \? | pty vi ]
  [ questions the solution ]

I did mention that you have to set up appropriate macros as well, and
turn off keyboard interrupts. The only thing that you can't completely
control from within vi is the mapping of the colon---and my solution
handles that.

---Dan