From owner-freebsd-current Fri Oct 23 19:38:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06099 for freebsd-current-outgoing; Fri, 23 Oct 1998 19:38:24 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06094 for ; Fri, 23 Oct 1998 19:38:21 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA20100 for ; Sat, 24 Oct 1998 12:07:48 +0930 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA30610; Sat, 24 Oct 1998 12:07:47 +0930 Date: Sat, 24 Oct 1998 12:07:47 +0930 (CST) From: Kris Kennaway To: current@FreeBSD.ORG Subject: nestea v2 against freebsd 3.0-Release (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tested this against myself this morning and it panicked the machine - I had to run as root to hit the 127.0.0.1 target, but perhaps someone could confirm whether it works against remote machines? This is obviously not good to have amajor vulnerability in 3.0 known before it even ships out the door :-( Kris ---------- Forwarded message ---------- Date: Fri, 23 Oct 1998 09:41:23 +0200 From: Gilles Bruno To: freebsd-security@freebsd.org Subject: nestea v2 against freebsd 3.0-Release Hi everyone, we tested yesterday the old nestea v2 against a brand new 3.0-Release : it has prooved to be effective against it (the box rebooted - invalid page fault while in kernel mode). The same test against 2.2.[6,7]-Release didn't harm at all. Am I missing something ? some sysctl ? a special kernel config ? Let us know... 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-current" in the body of the message