Editor With NO Shell Access?

[Michael Sierchio]

There are two edits to make to ex_shell.c in /usr/src/contrib/nvi/ex that
will prevent a shell from being executed.

99,100c
return (1);
.
48,51c
return (1);
.


On Mon, Mar 12, 2012 at 4:59 PM, David Brodbeck <gull at gull.us> wrote:

> On Mon, Mar 12, 2012 at 7:19 PM, Tim Daneliuk <tundra at tundraware.com>
> wrote:
> > I have a situation where I need to provide people with the ability to
> edit
> > files.  However, under no circumstances do I want them to be able to exit
> > to the shell.   The client in question has strong (and unyielding)
> InfoSec
> > requirements in this regard.
>
> I vaguely recall that pico can be configured to work this way.  Check
> out /usr/ports/editors/pico-alpine.  Sorry I can't give much more
> help; it's been a very long time since I worked with that particular
> editor.
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> freebsd-questions-unsubscribe at freebsd.org"
>