From owner-freebsd-security Fri Feb 12 16:28:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00776 for freebsd-security-outgoing; Fri, 12 Feb 1999 16:28:09 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.149.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00727 for ; Fri, 12 Feb 1999 16:28:00 -0800 (PST) (envelope-from avalon@cheops.anu.edu.au) Received: (from avalon@localhost) by cheops.anu.edu.au (8.9.1/8.9.1) id LAA22086; Sat, 13 Feb 1999 11:27:48 +1100 (EDT) From: Darren Reed Message-Id: <199902130027.LAA22086@cheops.anu.edu.au> Subject: Re: IP Filter 3.2.10 To: thomas@pmpro.com (Mark Thomas) Date: Sat, 13 Feb 1999 11:27:48 +1100 (EDT) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: <3.0.6.32.19990212132744.00903220@pmpro.com> from "Mark Thomas" at Feb 12, 99 01:27:44 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In some mail from Mark Thomas, sie said: > > At 12:19 AM 2/13/99 +1100, Darren Reed wrote: > > > >You get that change because somebody decided to make an arbitrary change > >to the way certain structures were placed in include files, doing nothing > >more than breaking compatibility with various packages such as IP Filter, > >tcpdump, etc. > > > >To those who made it, don't bother trying to brainwash me, we've already > >been through the explanation cycle (which I still don't accept but with > >which you guys now need to live with). > > Er, what does this imply for the status of ipfilter in the near future? There is already an adapted version for 3.0 available now which will be merged soon. Darren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message