Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!samsung!emory!hubcap!ncrcae!ncr-sd!simasd!jadpc!jdeitch
From: jdeitch@jadpc.cts.com (Jim Deitch)
Newsgroups: comp.unix.sysv386
Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386
Keywords: BAD BUG
Message-ID: <1991Feb16.085716.1243@jadpc.cts.com>
Date: 16 Feb 91 08:57:16 GMT
References: <1991Feb11.184130.11321@jwt.UUCP> <1991Feb12.020625.6779@kithrup.COM> <1991Feb13.220110.1314@scuzzy.in-berlin.de>
Organization: Network Engineering Technologies, San Diego, CA.
Lines: 30

In article <1991Feb13.220110.1314@scuzzy.in-berlin.de> src@scuzzy.in-berlin.de (Heiko Blume) writes:
>sef@kithrup.COM (Sean Eric Fagan) writes:
>>Get SCO.  It does not have this "feature," and still manages to support
>>Weitek coprocessors (the coprocessor the original poster was referring to, I
>>believe).  (The Weitek's use memory for registers and, obviously, need to be
>>able to write them.  The weitek registers are stuck in the upage, and
>>happen, in apparantly every 3.2 save SCO's, to be in the same page as the
>>uid stuff.  *Bad*.  *Very* bad.)
>
>there's no problem with ISC if you have any co-processor. the problem is the
>floating point emulation that runs in user space and needs to write the u area. 
>
>i hope ISC will send me a 'bug fix' in the form of a 33MHz 80387 :-)

Me Too!

One quick question though,
  I tried to fix the problem temporarily by setting UAREARW to 0 as
was posted.  I rebult the kernel and all was well, until cnews tried
to run.  I got a core dump from sendbatches.  Also the dfspace utility
would not work.  Anyone else seen this?  I am running ISC 2.2 w/o a
coprocessor.  Do I also have to set UAREAUS to 0 to make this "fix"
work?

Jim

-- 
ARPANET:    jadpc!jdeitch@nosc.mil
INTERNET:   jdeitch@jadpc.cts.com
UUCP:	    nosc!jadpc!jdeitch