Date: Tue, 08 May 2007 08:35:14 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Stevan Tiefert <stevan_tiefert@yahoo.de> Cc: ports@freebsd.org Subject: Re: How to prevent make compiling a binary? Message-ID: <448xbzv6gt.fsf@Lowell-Desk.lan> In-Reply-To: <1178625043.892.16.camel@vagabund.w33> (Stevan Tiefert's message of "Tue\, 08 May 2007 13\:50\:34 %2B0200") References: <1178550334.6653.9.camel@vagabund.w33> <20070507201247.e3f834cc.stas@FreeBSD.org> <1178565933.5854.1.camel@vagabund.w33> <46401290.7080000@gmx.de> <1178619731.892.4.camel@vagabund.w33> <20070508114319.GG838@turion.vk2pj.dyndns.org> <1178625043.892.16.camel@vagabund.w33>
next in thread | previous in thread | raw e-mail | index | archive | help
Stevan Tiefert <stevan_tiefert@yahoo.de> writes: > Am Dienstag, den 08.05.2007, 21:43 +1000 schrieb Peter Jeremy: >> On 2007-May-08 12:22:03 +0200, Stevan Tiefert <stevan_tiefert@yahoo.de> wrote: >> > The port wouldn't be necessary when the >> >compat3x-port didn't stopped. >> >> The last FreeBSD 3.x release was 3.5.1 in July 2000. 3.x support has >> long since ceased and it is no longer possible to correct security >> holes in the compat3x port. Since a variety of security holes are >> known to exist, the port has been FORBIDDEN. >> >> Your options appear to be: >> 1) Contact mbrola@tcts.fpms.ac.be and get them to update the FreeBSD >> binaries to support 6.x >> 2) Override the 'FORBIDDEN' tag and install compat3x anyway. >> 3) Run the Linux version. >> > > 4) I build a port with this only needed lib in it. Already done: > http://www.freebsd.org/cgi/query-pr.cgi?pr=112499 But that still installs the standard C library with the vulnerability in it. In what way is that better (or even significantly different) than option 2?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?448xbzv6gt.fsf>