Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!wuarchive!julius.cs.uiuc.edu!rpi!masscomp!peora!tarpit!bilver!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386
Keywords: BAD BUG
Message-ID: <1991Feb11.184130.11321@jwt.UUCP>
Date: 11 Feb 91 18:41:30 GMT
References: <KR3NBQQ@dobag.in-berlin.de>
Organization: Private System -- Orlando, FL
Lines: 9

In article <KR3NBQQ@dobag.in-berlin.de> lumpi@dobag.in-berlin.de (Joern Lubkoll) writes:
>it seems that your very cute interactive unix System has a nice bug !

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?
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)