From owner-freebsd-security Tue May 4 13:54:32 1999 Delivered-To: freebsd-security@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E18FD14F78; Tue, 4 May 1999 13:54:26 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA11194; Tue, 4 May 1999 14:53:42 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04656; Tue, 4 May 1999 14:53:34 -0600 (MDT) Message-Id: <199905042053.OAA04656@harmony.village.org> To: Vince Vielhaber Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) Cc: Seth , freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG In-reply-to: Your message of "Mon, 03 May 1999 19:40:59 EDT." References: Date: Tue, 04 May 1999 14:53:34 -0600 From: Warner Losh Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message Vince Vielhaber writes: : It's typically in bad taste to post it to BugTraq before contacting the : vendor. I can say that no one appears to have contacted security-officer about this. People have contacted us in the past saying that their machine randomly reboots. When pressed for details, or to enable ddb or crash dumps to see why the machine is rebooting, they disappear and nothing further is heard from them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message