Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!elroy.jpl.nasa.gov!usc!snorkelwacker.mit.edu!shelby!msi.umn.edu!cs.umn.edu!quest!digibd!rhealey
From: rhealey@digibd.com (Rob Healey)
Newsgroups: comp.unix.sysv386
Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386
Keywords: BAD BUG
Message-ID: <1991Feb22.182013.13406@digibd.com>
Date: 22 Feb 91 18:20:13 GMT
References: <3227@sixhub.UUCP> <1991Feb18.175533.12275@kithrup.COM> <1991Feb20.005322.24769@scuzzy.in-berlin.de>
Organization: DigiBoard Incorporated, St. Louis Park, MN
Lines: 15

In article <1991Feb20.005322.24769@scuzzy.in-berlin.de> src@scuzzy.in-berlin.de (Heiko Blume) writes:
>>SCO managed to get it working before their first release; AT&T and Dell
>>managed to get it "fixed" for their second release.  All without having to
>>redesign an enormous program written entirely in assembly.  Or would you
>>rather that the fpu emulator have more bugs introduced?
>well, HOW did they fix it???

	I'll take a flying leap blind guess and say that they probably
	moved the location of the "registers"/"code" to a seperate
	page in memory that could have different MMU tags from the u block.

	This would seem to be the obvious solution, but again, it's just
	a guess.

		-Rob