From owner-freebsd-stable Tue May 4 9:34:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 8BFC914EC9 for ; Tue, 4 May 1999 09:34:27 -0700 (PDT) (envelope-from tom@embt.com) Received: from gizmo (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id QAA24121 for ; Tue, 4 May 1999 16:28:55 GMT (envelope-from tom@embt.com) Message-Id: <3.0.3.32.19990504123700.00e8091c@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 04 May 1999 12:37:00 -0400 To: freebsd-stable@freebsd.org From: Tom Embt Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, > > Sorry to be so vague, but I wanted to let everyone know, > > It's been demonstrated to me by two people who will not reveal "how" >that there is a remote bug exploit, almost certainly over IP, that will >cause FreeBSD-3.1 systems to reboot with no warnings. > >-jamie I've a hunch I've just been victim to this. I just noticed my 3.1-STABLE box isn't running RC5 anymore, then noticed the uptime of 0+12:34:12, which is certainly not right. dmesg shows the typical WARNING: / was not properly dismounted message. I was asleep at the supposed reboot time, but my brother who was in the room says he did hear the CD-changer making some noise (which it does upon bootup). Another Win98 machine on the same power line was up and running continuously. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message