Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!agate!shelby!portia!forel!karish
From: karish@forel.stanford.edu (Chuck Karish)
Newsgroups: comp.unix.xenix
Subject: Re: SCO 3.2 UNIX
Summary: Security (mis)features
Message-ID: <6212@portia.Stanford.EDU>
Date: 29 Oct 89 06:34:22 GMT
References: <3447@netcom.UUCP>
Sender: USENET News System <news@Portia.stanford.edu>
Reply-To: karish@forel.stanford.edu (Chuck Karish)
Distribution: usa
Organization: Mindcraft, Inc.
Lines: 11

In article <3447@netcom.UUCP> bobr@netcom.UUCP (R. Rieger) wrote:
>I found one other bug that was a real problem!  For some reason and
>I still do not know why,  a file named /etc/auth/system/tty-t would
>get created.  Once created,  no one could login.

SCO UNIX 3.2 has some security extensions beyond standard UNIX practice.
This may be one of them.  There's a choice in one of the
sysadm menus to disable all the security extensions.

	Chuck Karish		karish@mindcraft.com
	(415) 493-9000		karish@forel.stanford.edu