From owner-freebsd-security Fri Jan 21 8:41:15 2000 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id 8210B15261 for ; Fri, 21 Jan 2000 08:41:12 -0800 (PST) (envelope-from brett@lariat.org) Received: from workhorse (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id JAA20265; Fri, 21 Jan 2000 09:40:53 -0700 (MST) Message-Id: <4.2.2.20000121093753.01a51ba0@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 21 Jan 2000 09:40:50 -0700 To: Reinier Bezuidenhout , robinson@netrinsics.com (Michael Robinson) From: Brett Glass Subject: Re: stream.c workaround clarification Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <200001210946.LAA15150@oskar.dev.nanoteq.co.za> References: <200001210849.QAA01513@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 02:46 AM 1/21/2000 , Reinier Bezuidenhout wrote: >Hi .. > >Is there any similar rules in IPFW that simulates this ?? As I suspected, this is going to be the number one FAQ about this 'sploit. No, IPFW can't do it without assistance from another program, which has not yet been written. --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message