Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!tut.cis.ohio-state.edu!usenet.ins.cwru.edu!ncoast!allbery
From: allbery@NCoast.ORG (Brandon S. Allbery KB8JRR)
Newsgroups: comp.unix.sysv386
Subject: Re: SCO UNIX C2 Security Issues
Message-ID: <1990Dec30.023255.25585@NCoast.ORG>
Date: 30 Dec 90 02:32:55 GMT
References: <277916E3.2042@tct.uucp> <29044@usc> <1990Dec29.005544.6641@robobar.co.uk>
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery KB8JRR)
Followup-To: comp.unix.sysv386
Organization: North Coast Computer Resources (ncoast)
Lines: 20

As quoted from <1990Dec29.005544.6641@robobar.co.uk> by ronald@robobar.co.uk (Ronald S H Khoo):
+---------------
| Does anyone know if u_secclass does anything in the current SCO releases ?
| I remember someone saying that making it "d" and rebooting made a difference
| to them (was it Brandon?) but I can't seem to find any difference.
+---------------

u_secclass=d disables checking of the secure files database (which otherwise
causes major complaints if you ever dare to change things without updating the
file lists to match; it screams bloody murder about security violations).  I
had hoped it would also disable luid's, but it doesn't.

++Brandon


-- 
Me: Brandon S. Allbery			    VHF/UHF: KB8JRR 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