From owner-freebsd-current Wed Dec 20 22:35:28 2000 From owner-freebsd-current@FreeBSD.ORG Wed Dec 20 22:35:25 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 0B9BF37B402; Wed, 20 Dec 2000 22:35:16 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id eBL6Z7e95656; Thu, 21 Dec 2000 08:35:07 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200012210635.eBL6Z7e95656@zibbi.icomtek.csir.co.za> Subject: Re: Is compatibility for old aout binaries broken? In-Reply-To: <20001220221132.S79112@shale.csir.co.za> from Jeremy Lea at "Dec 20, 2000 10:11:33 pm" To: reg@FreeBSD.ORG (Jeremy Lea) Date: Thu, 21 Dec 2000 08:35:07 +0200 (SAT) Cc: kris@FreeBSD.ORG (Kris Kennaway), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Wed, Dec 20, 2000 at 07:13:05PM -0800, Kris Kennaway wrote: > > Argh. I'm going to have to mark that port FORBIDDEN, then, because old > > versions of the X libraries have remote vulnerabilities. > > Hmmm... Are there patches available to just fix the security problems? > We can't move much beyond 3.3.3 because Netscape's released aout > binaries have workarounds for bugs from before then, which cause them to > be unstable when those bugs are fixed. Maybe we should find out who the good guy is that is building the FreeBSD versions of Netscape and help him upgrade his version of FreeBSD or get him a new machine with FreeBSD 4.2 on it? > > Else, I guess we are stuck with netscape-linux or mozilla... And people > keep breaking mozilla... Well there is the bsdi version too... John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message