From owner-freebsd-current Mon Nov 17 20:59:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18612 for current-outgoing; Mon, 17 Nov 1997 20:59:26 -0800 (PST) (envelope-from owner-freebsd-current) Received: from shell.dragondata.com (toasty@shell.dragondata.com [204.137.237.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18601 for ; Mon, 17 Nov 1997 20:59:22 -0800 (PST) (envelope-from toasty@shell.dragondata.com) Received: (from toasty@localhost) by shell.dragondata.com (8.8.7/8.8.7) id XAA21433; Mon, 17 Nov 1997 23:01:47 -0600 (CST) (envelope-from toasty) From: User Toasty Message-Id: <199711180501.XAA21433@shell.dragondata.com> Subject: Re: teardrop In-Reply-To: from Tom at "Nov 17, 97 07:35:49 pm" To: tom@uniserve.com (Tom) Date: Mon, 17 Nov 1997 23:01:47 -0600 (CST) Cc: mcdougall@ameritech.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > On Mon, 17 Nov 1997, Adam McDougall wrote: > > > Has this new kind of nuke been addressed, and can it be/has it been > > fixed? I just cvsupped sunday, is mine fixed? thanks. > > > Perhaps you explain what the hell "teardrop" is, and why we should care. > > Tom > Teardrop is someone's name for a new nuke that affects Linux, BSDI, Windows 95 and Windows NT. It involves sending bad TCP/IP fragments. FreeBSD is immune to the attack, so, to answer his question: "Yes and No". No, nothing has been addressed, but you copy is 'fixed'. :) Kevin