Date: Mon, 12 Mar 2012 17:15:11 -0700 From: Michael Sierchio <kudzu@tenebras.com> To: David Brodbeck <gull@gull.us> Cc: Tim Daneliuk <tundra@tundraware.com>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Editor With NO Shell Access? Message-ID: <CAHu1Y71rTM6hk_MC9WB8-r_=2f=hEVTV1ECRqCFr0iW%2B9EZV9w@mail.gmail.com> In-Reply-To: <CAHhngE0vQRfb8j893iRN3-W-Y%2BV5aB5Ekyw3apBJNzpCN8XAPw@mail.gmail.com> References: <4F5E4C2A.1020005@tundraware.com> <CAHhngE0vQRfb8j893iRN3-W-Y%2BV5aB5Ekyw3apBJNzpCN8XAPw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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@gull.us> wrote: > 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 > 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHu1Y71rTM6hk_MC9WB8-r_=2f=hEVTV1ECRqCFr0iW%2B9EZV9w>