From owner-freebsd-ports Mon Feb 14 9:36:12 2000 Delivered-To: freebsd-ports@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by builder.freebsd.org (Postfix) with ESMTP id 5D2AF4BD6 for ; Mon, 14 Feb 2000 09:36:10 -0800 (PST) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 02C9C9B17; Mon, 14 Feb 2000 12:36:23 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id EA1F6BA1D; Mon, 14 Feb 2000 12:36:23 -0500 (EST) Date: Mon, 14 Feb 2000 12:36:23 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Christophe Prevotaux Cc: ports@FreeBSD.org Subject: Re: Hylafax In-Reply-To: <38A830B8.6CD60113@hexanet.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 14 Feb 2000, Christophe Prevotaux wrote: > How come Hylafax is marked as FORBIDDEN in the Makefile ? > Does anyone knows how to fix that problem ? > 1.30 Fri Jan 7 13:07:00 2000 by asami Diffs to 1.29 Change BROKEN to FORBIDDEN, there is a security hole. _________________________________________________________________ 1.29 Wed Dec 1 19:22:23 1999 by kris CVS Tags: RELEASE_3_4_0 Diffs to 1.28 Mark BROKEN due to buffer overflow yielding setuid uucp Note that this port currently has no MAINTAINER, so will probably stay broken until it either gets upgraded or fixed by someone who actually uses it. If you search the BugTraq archives, you should be able to find what exactly the problems are. As stated above, unless someone who actually uses it decided to fix it, it will be BROKEN/FORBIDDEN until... ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message