Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!altos!altos86!steve
From: steve@altos86.Altos.COM (Steve Scherf)
Newsgroups: comp.unix.sysv386
Subject: Re: setluid(0) in SCO ?
Summary: Altos' solution to C2
Keywords: Defeat SCO C2 Security
Message-ID: <4111@altos86.Altos.COM>
Date: 26 Sep 90 00:23:03 GMT
References: <1990Sep20.163355.7147@robobar.co.uk> <738@tetrauk.UUCP>
Reply-To: steve@Altos.COM (Steve Scherf)
Organization: Altos Computer Systems, San Jose, CA
Lines: 19

In article <738@tetrauk.UUCP> paul@tetrauk.UUCP (Paul Ashton) writes:
>In article <2434@maestro.htsa.aha.nl> fransh@maestro.htsa.aha.nl (Frans van Hattem) writes:
>>I'm trying to use 'ct' under SCO UnixV.3.2 but it won't work?; :-(
>>Everything goes well, but when I have to login again (after I'v been called back) I get an error:
>>	"Bad login user id"
>
>When login runs it expects to be able to call setluid(S) to set the immutable
>login user id, which can never after be changed. Unfortunately since your
>luid has already been set, this will fail and bomb out.

In Altos Unix, if you have C2 relaxed you can call setluid() as often as
you want. The annoying thing is 'ct' still doesn't work! (for other reasons)
I don't understand why they even bother to ship a utility that will never
work.
-- 
Steve Scherf
steve@Altos.COM    ...!{sun|sco|pyramid|amdahl|uunet}!altos!steve

These opinions are solely mine, but others may share them if they like.