Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/KT)
Newsgroups: comp.unix.sysv386
Subject: Re: Which UNIX?
Message-ID: <1990Sep19.011303.13481@NCoast.ORG>
Date: 19 Sep 90 01:13:03 GMT
References: <1990Sep16.021512.17218@NCoast.ORG> <5J9LP1w163w@mudos.ann-arbor.mi.us>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/KT)
Followup-To: comp.unix.sysv386
Organization: North Coast Public Access *NIX, Cleveland, OH
Lines: 24

As quoted from <5J9LP1w163w@mudos.ann-arbor.mi.us> by mju@mudos.ann-arbor.mi.us (Marc Unangst):
+---------------
| allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/KT) writes:
| > Never mind "buggy" --- SCO UNIX has C2-much [ ;-) ] security for most users.
| > ESPECIALLY on a public access site, unless you plan to be a fascist sysadmin.
| > ("Fascist"?  Not even Hitler was as bad as C2 security can be --- and
| > configuring it is a major pain, even with the sysadmsh.)
| 
| Huh?  When you install SCO Unix, you are given the choice of whether
| or not you want C2 security enabled.  Even if you choose "yes", you
| can still disable it later on.  Use the /etc/relax command.
+---------------

You missed a thread from about a month ago.  I *have* relaxed security; I
installed it that way.  Unfortunately, this didn't stop it from screaming
about security violations when I attempted to add a new shell to the sysadmsh
list of configurable login shells.  Among other things.

++Brandon
-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR/KT on 220, 2m, 440
Internet: allbery@NCoast.ORG		    Packet: KB8JRR @ WA8BXN
America OnLine: KB8JRR			    AMPR: KB8JRR.AmPR.ORG [44.70.4.88]
uunet!usenet.ins.cwru.edu!ncoast!allbery    Delphi: ALLBERY