SECURITY BUG IN INTERACTIVE UNIX SYSV386

Sean Eric Fagan sef at kithrup.COM
Tue Feb 12 13:06:25 AEST 1991


In article <1991Feb11.184130.11321 at jwt.UUCP> john at jwt.UUCP (John Temples) writes:
>Yikes.  This also works on ESIX-D without a coprocessor, and on ISC 2.0.2
>*with* a coprocessor.  It failed on Microport 2.2 with a coprocessor.
>Now, the question is, what do we do to protect ourselves in the meantime?

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.)

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef at kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.



More information about the Comp.unix.sysv386 mailing list