From owner-freebsd-stable Tue Aug 11 04:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19163 for freebsd-stable-outgoing; Tue, 11 Aug 1998 04:48:54 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from stcgate.statcan.ca (stcgate.statcan.ca [142.206.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19150 for ; Tue, 11 Aug 1998 04:48:49 -0700 (PDT) (envelope-from jeays@statcan.ca) Received: from stcinet (stcinet.statcan.ca [142.206.128.146]) by stcgate.statcan.ca (8.9.1/8.6.9) with SMTP id HAA18279; Tue, 11 Aug 1998 07:53:40 -0400 (EDT) Received: from statcan.ca by statcan.ca (SMI-8.6/SMI-SVR4) id HAA20967; Tue, 11 Aug 1998 07:51:46 -0400; sender jeays@statcan.ca Date: Tue, 11 Aug 1998 07:47:46 -0400 (EDT) From: Mike Jeays X-Sender: jeays@austral To: Scott cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Huge Bug in FreeBSD not fixed? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a 'me too'. This program crashed my Pentium 120 (48MB) each time I ran it from within an X-term, but not when I ran it from another TTY. In the latter case it reported '38 processes' or '47 processes' terminated normally. It was a hard crash - the cursor froze for a few moments, then the screen went black and the machine rebooted. The first time it crashed, fsck produced a number of 'salvaging...' messages; the second time, it just had to reset the clean flag in the superblock, on each of my filesystems. Version is 2.2.7, as installed from the CheapBytes CD. Jordan - maybe this should not be dismissed too quickly? On Tue, 11 Aug 1998, Scott wrote: > I ran across this bug a while back on rootshell, and then again by a user > on IRC who offered to take down my box. Soon after that, the bug was fixed > and things were fine. But just out of boredom, i decided to run the > exploit again. Sure enough, i had a kernel panic and that was it. All of > this from a normal user account. The bug has reoccured recently and may > cause problems on my server if the users find out about the vulnerability. > > I am running FreeBSD 2.2.7-STABLE (Last compiled on August 5th early in > the morning). The system is running on a PII233 with 64MB RAM. This bug > REALLY needs to be fixed ASAP. > > I would like to know if other systes are vulnerable as well. I discussed > this matter on IRC and everyone said they had similar problems. This bug > needs to be addressed soon. I would HATE switching to linux because my > system keeps crashing. > > > --------------- > Scott Swindells, SchematiX.NET > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message