From owner-freebsd-stable Tue May 4 7:35: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from delenn.acm.rpi.edu (delenn.acm.rpi.edu [128.213.5.14]) by hub.freebsd.org (Postfix) with SMTP id D5BBD15689 for ; Tue, 4 May 1999 07:34:51 -0700 (PDT) (envelope-from slk@acm.rpi.edu) Received: (qmail 27021 invoked by uid 1120); 4 May 1999 14:34:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 4 May 1999 14:34:51 -0000 Date: Tue, 4 May 1999 10:34:50 -0400 (EDT) From: Simon Karpen To: Raymond Wiker Cc: freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) In-Reply-To: <14126.49715.589157.172436@foobar.orion.no> 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 On Tue, 4 May 1999, Raymond Wiker wrote: > I have two other machines running 3.1-RELEASE in a slightly > less hostile environment (i.e, no direct connections outwards), and > they have been much more stable. I cannot rule out a hardware problem > on the 486; I'll know for sure as soon as I upgrade it. I have 3.1-STABLE in a fairly hostile network environment. I've found that the following will make the system unstable and reboot. If you avoid all of thses, it's solid as a rock. (otherwise you get the reboots) VESA support VM86 support OSS/Payware sound drivers With any of thses, the system will reboot anywhere from a few minutes to a day or two after being brought up, usually within a few hours. With all of these removed, it's stable. The system is a PII/266 192MB with SCSI disks on a Buslogic, a Tulip (de0) ethernet card, Matrox G200 video, and a Creative Vibra16Xv soundcard. --Simon -- Simon Karpen karpes@rpi.edu slk@acm.rpi.edu #include I don't speak for RPI in any way. "Those that give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." --Ben Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message