Protecting against downloads

[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 your
>policy towards shell access?

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.

bill


-- 
Work:    heiser at tdw201.ed.ray.com
	 {decuac,necntc,uunet}!rayssd!tdw201!heiser
Home(1): bill%unixland.uucp at world.std.com -or- uunet!world!unixland!bill
	 Public Access Unix Coming Soon!
Home(2): Bill.Heiser at f240.n322.z1.fidonet.org (BBS: 1-508-655-3848)
Other:	 heiser at world.std.com     (Pub. Access Unix)