Xref: utzoo alt.security:1561 alt.bbs:2957 comp.unix.sysv386:449 Path: utzoo!attcan!uunet!rayssd!sud509!heiser@tdw201.ed.ray.com From: heiser@tdw201.ed.ray.com Newsgroups: alt.security,alt.bbs,comp.unix.sysv386 Subject: Re: Protecting against downloads Message-ID: <2441@sud509.ed.ray.com> Date: 17 Sep 90 15:35:14 GMT References: <8RFgP2w163w@mudos.ann-arbor.mi.us> Sender: heiser@sud509.ed.ray.com (Bill Heiser - Unix Sys Admin @ Raytheon Company, Sudbury MA) Organization: Raytheon Company, Sudbury MA Lines: 23 In article epeterson@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@tdw201.ed.ray.com {decuac,necntc,uunet}!rayssd!tdw201!heiser Home(1): bill%unixland.uucp@world.std.com -or- uunet!world!unixland!bill Public Access Unix Coming Soon! Home(2): Bill.Heiser@f240.n322.z1.fidonet.org (BBS: 1-508-655-3848) Other: heiser@world.std.com (Pub. Access Unix)