From owner-freebsd-security Tue May 4 20:39:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 18F3E15298; Tue, 4 May 1999 20:39:23 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id VAA18567; Tue, 4 May 1999 21:39:08 -0600 (MDT) Message-Id: <4.2.0.37.19990504213441.045d6c50@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.37 (Beta) Date: Tue, 04 May 1999 21:37:59 -0600 To: Jorge Aldana , Mike Uttech From: Brett Glass Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) Cc: freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG In-Reply-To: References: <19990504210951.3781215C1E@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We had kernel panics resulting in spontaneous reboots in 2.2.7 when we removed the ATAPI_STATIC option. The swap partition was on an IDE drive, so we figured that the problem was VM-related. I sent information to a few lists sometime back, but I don't know if any of the core team members ever followed up. We haven't dared to remove that option since. --Brett At 05:18 PM 5/4/99 -0700, Jorge Aldana wrote: >So, rebooting when a machine is overloaded is not a problem? > >It seems (from the current and past questions to security and questions >mail lists) that something is going on with this. Just because we can't >solve it doesn't mean its not there, mysterious re-boots seem to be >occuring at my site off and on. As soon as we up the debuging nothing >happens (this alone changes a variable within the system), as most sites >and people I've talked to we lack time, from debuging and actually keeping >the systems running. I have seen too many variables in determining what >caused a system to crash and repeating a case never has resulted in a >reproduction of said problem. > >It seems from the responses that this is an acceptable symptom of FreeBSD >3.1 (release and stable)? > > >From my logs, machines have stayed up since FreeBSD 3.1 Stable was >installed (19990303) and others have rebooted the next day and all >combinations in between (but none are consistent). > >It may or may not help but that has been my experince. > >Jorge > >On Tue, 4 May 1999, Mike Uttech wrote: > > > We used to have problems with one of our 3.1-RELEASE boxes randomly > > locking up with no logs of why. We decided to split the load off of the > > one machine and have not had a problem with it locking up since. If my > > memory serves me today, I remember reading about a problem in the > > 3.1-RELEASE distribution that under heavy load caused the system to hang or > > reboot. I personally feel that many of these people (the ones who are > > saying they have been having random reboots) are not being attacked in > > anyway but rather are having their machines overloaded and rebooting. > > > > > > Mike > > > > > > At 03:53 PM 5/4/99 , Warner Losh wrote: > > >In message Vince Vielhaber writes: > > >: It's typically in bad taste to post it to BugTraq before contacting the > > >: vendor. > > > > > >I can say that no one appears to have contacted security-officer about > > >this. People have contacted us in the past saying that their machine > > >randomly reboots. When pressed for details, or to enable ddb or crash > > >dumps to see why the machine is rebooting, they disappear and nothing > > >further is heard from them. > > > > > >Warner > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-security" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-security" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message