From owner-freebsd-security Thu Feb 1 13:52:43 2001 Delivered-To: freebsd-security@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 85D8B37B491 for ; Thu, 1 Feb 2001 13:52:26 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f11LkR357618; Thu, 1 Feb 2001 13:46:27 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010201130629.B74541@xor.obsecurity.org> Date: Thu, 01 Feb 2001 13:52:11 -0800 (PST) From: John Baldwin To: Kris Kennaway Subject: Re: FreeBSD Ports Security Advisory: FreeBSD-SA-01:07.xfree86 Cc: security@FreeBSD.org, Paul Andrews Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 01-Feb-01 Kris Kennaway wrote: > On Thu, Feb 01, 2001 at 12:57:26PM -0700, Paul Andrews wrote: >> Does this issue affect only those that installed the XFree86 3.3.6 port or >> does it also affect those who have installed FreeBSD 4.2 RELEASE. >> >> If it does affect the RELEASE version what is the easiest why to fix this >> problem, without upgrading to XFree86 4.01. > > My understanding is that the XFree86 distribution is built from > whatever is in ports at the time of release. In fact, doesn't > sysinstall just install the port thesedays anyway? > > ls -l /var/db/pkg/XFree86* > > Kris No, it builds the distribution from ports, and then engages in evilness to package up the bits in tarballs that mimic the normal XFree distributions. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message