Date: Wed, 5 May 1999 16:37:15 -0400 (EDT) From: Simon Karpen <slk@acm.rpi.edu> To: Mike Smith <mike@smith.net.au> Cc: Raymond Wiker <raymond@orion.no>, freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) Message-ID: <Pine.LNX.4.10.9905051633200.28381-100000@delenn.acm.rpi.edu> In-Reply-To: <199905051830.LAA01118@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[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 <std_disclaimer.h> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.9905051633200.28381-100000>