Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!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: <1991Feb13.204408.15621@kithrup.COM> Date: 13 Feb 91 20:44:08 GMT References: <1991Feb11.184130.11321@jwt.UUCP> <1739@svin02.info.win.tue.nl> Organization: Kithrup Enterprises, Ltd. Lines: 17 In article <1739@svin02.info.win.tue.nl> debra@info.win.tue.nl writes: >This (and other postings) suggests that the problem would be found >in the more generic sVr3.2 from AT&T. It was. Note that it was in the *original* release of 3.2 for the '386. >So it looks like somehow the same bug ended up in ESIX and ISC >(and AT&T sVr3.1?) but not in AT&T sVr3.2.1 or SCO. SCO noticed it and fixed it for their release of 3.2.0; ISC, ESIX, and others apparantly didn't notice it until later, if at all. -- 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.