From owner-freebsd-current  Tue Nov 18 15:25:14 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA04556
          for current-outgoing; Tue, 18 Nov 1997 15:25:14 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA04540
          for <current@freebsd.org>; Tue, 18 Nov 1997 15:24:58 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.210.252] 
	by pop.uniserve.com with smtp (Exim 1.73 #1)
	id 0xXx0i-000649-00; Tue, 18 Nov 1997 15:24:48 -0800
Date: Tue, 18 Nov 1997 15:24:46 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Niall Smart <njs3@doc.ic.ac.uk>
cc: Jason Young <doogie@forbidden-donut.anet-stl.com>,
        Adam McDougall <mcdougall@ameritech.net>, current@freebsd.org
Subject: Re: teardrop
In-Reply-To: <E0xXv9L-0000Br-00@oak47.doc.ic.ac.uk>
Message-ID: <Pine.BSF.3.96.971118152134.14635B-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 18 Nov 1997, Niall Smart wrote:

> freebsd-{current,hackers, stable,smp} before. Perhaps it should have
> been aimed at -questions however.

  Definitely.  If you are on hackers, or current, you should be capable of
building the exploit yourself, and trying it.

> Niall

Tom