From owner-freebsd-security Fri Aug 4 11:46:31 2000 Delivered-To: freebsd-security@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id CE30537BB92 for ; Fri, 4 Aug 2000 11:46:21 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id OAA56441; Fri, 4 Aug 2000 14:46:05 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Fri, 4 Aug 2000 14:46:05 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Slawek Zak Cc: freebsd-security@freebsd.org Subject: Re: IPFW + bridge fix. In-Reply-To: <87punodgrx.fsf@pf39.warszawa.sdi.tpnet.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 4 Aug 2000, Slawek Zak wrote: > Is anyone working on the fix for problem so irresponsibly reported to > bugtraq by Darren Reed. Is any security advisory going to be released. I'm not sure who else is working on this, but it is my plan to attempt to address these issues in the next few days; I was at IETF for the last week so didn't have access to a bridge test bed. Now that I'm back in DC I have test machines + network, I should make some progress. I'd like to see a general cleanup of the ipfw code, as although it is correct in most cases, it is hard to tell that by inspection. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message