From owner-freebsd-current  Sat Apr 11 23:27:06 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA25916
          for freebsd-current-outgoing; Sat, 11 Apr 1998 23:27:06 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25892
          for <current@freebsd.org>; Sat, 11 Apr 1998 23:27:05 -0700 (PDT)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id BAA00788
	for current@freebsd.org; Sun, 12 Apr 1998 01:27:01 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199804120627.BAA00788@home.dragondata.com>
Subject: f00f + SMP = ick
To: current@FreeBSD.ORG
Date: Sun, 12 Apr 1998 01:27:00 -0500 (CDT)
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I can pretty much confirm that SMP -current kernels are are still vulnerable
to the f00f attack...

Running the exploit once doesn't do anything... Putting it in a while loop,
and then putting the machine under heavy load will kill it though...

I've walked into my screensaver running with my chuck daemon just sitting
there 3 times now.

(rmusering another customer as we speak...)

Kevin

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message