Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cs.utexas.edu!chinacat!uudell!bigtex!james
From: james@bigtex.cactus.org (James Van Artsdalen)
Newsgroups: comp.unix.sysv386
Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386
Keywords: BAD BUG
Message-ID: <54805@bigtex.cactus.org>
Date: 19 Feb 91 07:29:46 GMT
References: <1991Feb15.134715.16979@virtech.uucp> <54663@bigtex.cactus.org> <1991Feb16.214824.2790@kithrup.COM> <1991Feb19.015227.26159@nuchat.sccsi.com>
Reply-To: james@bigtex.cactus.org (James Van Artsdalen)
Organization: Institute of Applied Cosmology, Austin TX
Lines: 33

In <1991Feb19.015227.26159@nuchat.sccsi.com>, steve@nuchat.sccsi.com
	(Steve Nuchia) wrote:

> In <1991Feb16.214824.2790@kithrup.COM> sef@kithrup.COM
	(Sean Eric Fagan) writes:

| you're using the emulator, you seem to have a multi-segment
| process).  Since it needs to keep the fp registers somewhere, and they
| are very much process-related, the "proper" place to keep them is in
| the u area, just like other registers.

> Unmitigated bullshit.

oh?  I see you haven't thought the problem through yet.

> The only technical justification for putting them there are
> 	1) so they get initialized at startup without additional
> 		code in exec.
> 	2) to avoid having to allocate a chunk of data space and
> 		figure out how to address it from the emulator.

Now, think about sdb, and then propose a solution.

Remember, we're not out to remove things from the u block, only to
make sure that important things aren't writable.  Those are very
different goals.

Also, remember that Sean is talking about SCO's *solution*, which
already works and is in the field.  Until yours is implemented and
working, don't be so quick to criticize.
-- 
James R. Van Artsdalen          james@bigtex.cactus.org   "Live Free or Die"
Dell Computer Co    9505 Arboretum Blvd Austin TX 78759         512-338-8789