From owner-freebsd-current Mon Nov 17 20:03:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA14516 for current-outgoing; Mon, 17 Nov 1997 20:03:34 -0800 (PST) (envelope-from owner-freebsd-current) Received: from forbidden-donut.anet-stl.com (forbidden-donut.anet-stl.com [209.83.128.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA14494 for ; Mon, 17 Nov 1997 20:03:26 -0800 (PST) (envelope-from doogie@forbidden-donut.anet-stl.com) Received: from localhost (doogie@localhost) by forbidden-donut.anet-stl.com (8.8.8/8.8.5) with SMTP id VAA27087; Mon, 17 Nov 1997 21:57:34 GMT Date: Mon, 17 Nov 1997 21:57:32 +0000 (GMT) From: Jason Young To: Adam McDougall cc: current@FreeBSD.ORG Subject: Re: teardrop In-Reply-To: <3470F4B7.2AC390D0@ameritech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- 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. Most/all of the *bsd TCP stacks were never vulnerable to this. This includes FreeBSD. I'm pretty sure that was in the original advisory. Jason Young ANET Chief Network Engineer -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQB1AwUBNHC9zaInE6ybC66VAQHZcQL9FAPyaeHb8MxvIFJnslypXgOvUk5wcpi/ a7dl5Fp1oWzxcIgGPvD6Co0o5AjmeEgQivZlToRZfH/mhxtwxV2AG09+X00CkU5I BXqgimNPcZdiBc4E/iuIOQlCWo8/0ysP =UFEL -----END PGP SIGNATURE-----