Re: LYNX-DEV securing Lynx for boxed-in environments.

[Benjamin C. W. Sittler]

You might consider running Lynx in a chroot'ed environment containing only
the commands you wish users to run.

Alternatively, you could make a new group, "untrusted", and chgrp all
untrusted executables to it. Any user who was allowed to run these
executables could be placed in this group. Finally, all the untrusted
executables could have their global exec permissions removed.

--
Benjamin C. W. Sittler - address@hidden - http://www.nmt.edu/~bsittler
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;