Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Mar 2012 23:59:54 +0000
From:      David Brodbeck <gull@gull.us>
To:        Tim Daneliuk <tundra@tundraware.com>
Cc:        FreeBSD Mailing List <freebsd-questions@freebsd.org>
Subject:   Re: Editor With NO Shell Access?
Message-ID:  <CAHhngE0vQRfb8j893iRN3-W-Y%2BV5aB5Ekyw3apBJNzpCN8XAPw@mail.gmail.com>
In-Reply-To: <4F5E4C2A.1020005@tundraware.com>
References:  <4F5E4C2A.1020005@tundraware.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 12, 2012 at 7:19 PM, Tim Daneliuk <tundra@tundraware.com> wrote=
:
> I have a situation where I need to provide people with the ability to edi=
t
> files. =A0However, under no circumstances do I want them to be able to ex=
it
> to the shell. =A0 The client in question has strong (and unyielding) Info=
Sec
> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHhngE0vQRfb8j893iRN3-W-Y%2BV5aB5Ekyw3apBJNzpCN8XAPw>