Protecting against downloads

[John Boteler]

>From article <2441 at sud509.ed.ray.com>, by heiser at tdw201.ed.ray.com:
> In article <epeterso.653316195 at houligan> epeterson at encore.com writes:
>>All in all, it ends up boiling down to the question "Why do you want
>>to give your users shell access?"  To let them use the tools on the
>>system to develop their own programs?  To learn Unix?  To experiment
>>with various applications?  How far do you trust them?
> What's a "public access unix" without shell access?  I want to provide
> access for all of the reasons you mentioned here.  If I wanted to 
> continue to ONLY allow access via a menu-driven program, I'd have no
> reason to switch from my current dos bbs.


This sounds like 'Public Administration 101' all over again.

Want benefits? Accept risks!





-- 
John Boteler   bote at csense.uucp           {uunet | ka3ovk}!media!csense!bote
SkinnyDipper's Hotline: 703-241-BARE | VOICE only, Touch-Tone(TM) signalling