Xref: utzoo alt.security:1614 comp.unix.sysv386:662
Path: utzoo!utgpu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!mips!apple!olivea!orc!inews!iwarp.intel.com!gargoyle!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: alt.security,comp.unix.sysv386
Subject: Re: Here's how to stop shell escapes from vi
Message-ID: <1990Sep24.040745.10454@chinet.chi.il.us>
Date: 24 Sep 90 04:07:45 GMT
References: <11285:Sep2022:15:2090@kr <924@mwtech.UUCP> <27387:Sep2320:07:3890@kramden.acf.nyu.edu>
Organization: Chinet - Chicago Public Access UNIX
Lines: 17

In article <27387:Sep2320:07:3890@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>    [ trash the colon with pty -0 tr \: \? | pty vi ]
>
>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.

Umm... Well, there's 'Q' to go to ex mode and stay there while you
type sh, or if the tmp file that you start out with contains the
outlawed ":" and/or "!" characters (or you manage to read them in
from some other file) you can just edit them into the construction
you need, yank to a register and execute.  Leaves something to 
be desired as a form of security....

Les Mikesell
  les@chinet.chi.il.us