From owner-freebsd-stable Wed May 5 14:56:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from angel.double-barrel.be (mail.double-barrel.be [194.7.102.22]) by hub.freebsd.org (Postfix) with ESMTP id D264715047; Wed, 5 May 1999 14:56:11 -0700 (PDT) (envelope-from mvergall@double-barrel.be) Received: from double-barrel.be (ws1.double-barrel.be [194.7.102.29]) by angel.double-barrel.be (8.9.1b+Sun/8.9.1) with ESMTP id XAA01521; Wed, 5 May 1999 23:54:57 +0200 (MET DST) Message-ID: <3730BE71.B1D7B36F@double-barrel.be> Date: Wed, 05 May 1999 23:56:01 +0200 From: "Michael C. Vergallen" X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Seth Cc: "Michael C. Vergallen" , Tim Priebe , Greg Quinlan , freebsd-stable@FreeBSD.ORG, security@FreeBSD.ORG Subject: Re: FreeBSD 3.1 remote reboot exploit (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seth wrote: > Just out of curiosity, how were you attempting to remotely reboot your ftp > server? > Sending large packets , incomplete packets, small packets etc. I also only seen a FreeBSD box panic ones that is when I tripped on my server's cabling and pulled the Host adapter cable loose from the disc crate that was when I was transfering a large 1 GB file as a test to see if the TCP stack was upto scratch. Now the system paniced when trying to flush a block to disc.. Michael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message