From owner-freebsd-security  Tue May  4 22:39:32 1999
Delivered-To: freebsd-security@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 851D315C1C
	for <security@FreeBSD.ORG>; Tue,  4 May 1999 22:39:31 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA09233;
	Tue, 4 May 1999 22:39:04 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: Darren Reed <avalon@coombs.anu.edu.au>
Cc: dillon@apollo.backplane.com, des@ifi.uio.no, security@FreeBSD.ORG
Subject: Re: [Jamie Rishaw <jamie@exodus.net>] FreeBSD 3.1 remote reboot exploit 
In-reply-to: Your message of "Wed, 05 May 1999 12:57:12 +1000."
             <199905050257.MAA07852@cheops.anu.edu.au> 
Date: Tue, 04 May 1999 22:39:04 -0700
Message-ID: <9230.925882744@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> So at this point, are you or one of the other freebsd people going to
> post a reply to bugtraq requesting more information and/or denying that
> it is a problem until it can be proved more conclusively ?  Being on the
> cusp of a release & Usenix, this needs to be settled one way or another.

I can't speak for the others, but not being one of the security team
folks I can say that I have no plans to say anything publically about
this.

- Jordan


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