Xref: utzoo alt.security:1595 alt.bbs:3003 comp.unix.sysv386:566 Path: utzoo!utgpu!cs.utexas.edu!uunet!cos!hqda-ai!media!csense!bote From: bote@csense.uucp (John Boteler) Newsgroups: alt.security,alt.bbs,comp.unix.sysv386 Subject: Re: Protecting against downloads Message-ID: <1990Sep20.164637.15309@csense.uucp> Date: 20 Sep 90 16:46:37 GMT References: <2441@sud509.ed.ray.com> Organization: Common Sense Computing, McLean, VA. Lines: 23 From article <2441@sud509.ed.ray.com>, by heiser@tdw201.ed.ray.com: > 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 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@csense.uucp {uunet | ka3ovk}!media!csense!bote SkinnyDipper's Hotline: 703-241-BARE | VOICE only, Touch-Tone(TM) signalling