Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!gatech!prism!mailer.cc.fsu.edu!uflorida!novavax!ankh!branch!tree!wcr
From: wcr@tree.metrolink.com (W.c. Rothanburg)
Newsgroups: comp.unix.sysv386
Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386
Message-ID: <WCR.91Feb16134346@tree.tree.metrolink.com>
Date: 16 Feb 91 13:43:46 GMT
References: <529@jahangir.UUCP> <6A5NSZK@dobag.in-berlin.de>
	<WCR.91Feb14012138@tree.tree.metrolink.com>
	<1991Feb15.152036.17557@cbnewsl.att.com>
Sender: wcr@tree.metrolink.com
Organization: Metro Link, Incorporated.  Pompano Beach, FL.
Lines: 29
In-reply-to: ry@cbnewsl.att.com's message of 15 Feb 91 15:20:36 GMT

In article <1991Feb15.152036.17557@cbnewsl.att.com> ry@cbnewsl.att.com (ryerson.schwark) writes:

   >The only problem with setting UAREAUS and UAREAW to zero is you
   >cannot do any floating point operations without a co-processor.  
   >(I don't have a co-processor to try it with... <sigh>)
   >
   >We (at Metro Link) have found the AT&T Unix/386 appears to have the
   >same problem.  (I heard this second hand and don't know from whom.)  
   >
   Would you check which release you're running?  We've checked our 3.2
   systems and none of them have this problem, if you do, I'd like to
   hear about it. 

I've heard this information second hand (unfortunately.)  It was not
a system which we run.  When we get calls about our products, 
sometimes the discussions also include other topics, including
this one.  Is there a specific (older?) release that might have this
problem?  

Bill

--
Who  : Metro Link, Inc.
What : X11.R4. for ISC Unix 386/ix, SCO Unix/386, and Everex ESIX
Where: 2213 West Mc Nab Road, Pompano Beach,FL 33069
Sales: sales@metrolink.com
Email: wcr@metrolink.com
Phone: +1 305 970 7353 x927
Fax  : +1 305 970 7351