Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!wuarchive!csus.edu!beach.csulb.edu!nic.csu.net!csun!kithrup!sef From: sef@kithrup.COM (Sean Eric Fagan) Newsgroups: comp.unix.sysv386 Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386 Keywords: BAD BUG Message-ID: <1991Feb18.042427.9434@kithrup.COM> Date: 18 Feb 91 04:24:27 GMT References: <329@alderan.uucp> <3215@sixhub.UUCP> Organization: Kithrup Enterprises, Ltd. Lines: 20 In article <3215@sixhub.UUCP> davidsen@sixhub.UUCP (bill davidsen) writes: > Here's a though for you, since the bug is in the emulator, and you >have a coprocessor, could it be that the system isn't seeing the coproc, >and that when you find out why, not only will the bug go away, but the >system should be a tad faster, too. Bill, the bug is *not* in the emulator. It's in the way the entire system (kernel and emulator) were designed. I posted a longish article going into this in a bit of detail. The upshot is that no ISC system before 2.2 can be configured to "fix" it, and no ISC 2.2 system can be configured to fix it if the machine does not have an FPU (note that 486s have an FPU, so they're "safe," after being configured properly). -- Sean Eric Fagan | "I made the universe, but please don't blame me for it; sef@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.