Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!texsun!moxie!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.unix.sysv386 Subject: Re: SECURITY BUG IN INTERACTIVE UNIX SYSV386 Keywords: BAD BUG Message-ID: Date: 15 Feb 91 20:45:56 GMT References: <1991Feb11.184130.11321@jwt.UUCP> <1739@svin02.info.win.tue.nl> <1991Feb13.204408.15621@kithrup.COM> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 14 In article <1991Feb13.204408.15621@kithrup.COM> sef@kithrup.COM (Sean Eric Fagan) writes: > 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. It's not in the Bell Tech V.3.2, which is pretty much a straight copy of the AT&T V.3.2. It is my understanding that the ISC V.3.2 at least contains a fair amount of V.3.x (x<=1) code in it, and the ESIX product is based on the ISC product. -- Peter da Silva. `-_-' peter@ferranti.com +1 713 274 5180. 'U` "Have you hugged your wolf today?"