From owner-freebsd-security Wed May 5 13:37:28 1999 Delivered-To: freebsd-security@freebsd.org Received: from delenn.acm.rpi.edu (delenn.acm.rpi.edu [128.213.5.14]) by hub.freebsd.org (Postfix) with SMTP id 98C6B1545B for ; Wed, 5 May 1999 13:37:16 -0700 (PDT) (envelope-from slk@acm.rpi.edu) Received: (qmail 28385 invoked by uid 1120); 5 May 1999 20:37:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 May 1999 20:37:16 -0000 Date: Wed, 5 May 1999 16:37:15 -0400 (EDT) From: Simon Karpen To: Mike Smith Cc: Raymond Wiker , freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) In-Reply-To: <199905051830.LAA01118@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [me: VM86 + VESA = reboot] On Wed, 5 May 1999, Mike Smith wrote: > > Naturally, it'd be really handy if you actually qualified what it is > about these that cause your system to reboot. I'd be very dubious > about the simple presence of either of these items causing random > reboots, and the dearth of supporting information you've offered makes > it much harder to help you. Right now I'm preparing to ship the box, so I can't do any more detailed testing. Once it's in its new location next week (think end of semester), I'll do much more extensive testing. The only other piece of info I can give right now is that Realplayer/Linux plaing a high bitrate file was a good way to speed up the crash. Try VESA+VM86 in your kernel, boot up with a 640x480 splashscreen, and play stuff using Realplayer/Linux for half an hour or so. (maybe an hour or two) I'd be quite surprised if you didn't get a reboot. --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-security" in the body of the message