From owner-freebsd-security Fri Feb 12 10:24:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15559 for freebsd-security-outgoing; Fri, 12 Feb 1999 10:24:13 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from pmpro.com (dyn001043.belt.digex.net [199.125.237.27]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15554 for ; Fri, 12 Feb 1999 10:24:11 -0800 (PST) (envelope-from thomas@pmpro.com) Received: from squash.pmpro.com (squash.pmpro.com [192.168.201.254]) by pmpro.com (8.6.13/8.6.12) with SMTP id NAA11952 for ; Fri, 12 Feb 1999 13:21:34 -0500 Message-Id: <3.0.6.32.19990212132744.00903220@pmpro.com> X-Sender: thomas@pmpro.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 12 Feb 1999 13:27:44 -0500 To: freebsd-security@FreeBSD.ORG From: Mark Thomas Subject: Re: IP Filter 3.2.10 In-Reply-To: <199902121319.AAA16011@cheops.anu.edu.au> References: <36c3916b.47ec.0@csi-x.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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? ----- Mark Mark Thomas -- pmpro, inc. -- thomas@pmpro.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message