From owner-freebsd-questions Thu Mar 30 6:52:21 2000 Delivered-To: freebsd-questions@freebsd.org Received: from radagast.wizard.net (radagast.wizard.net [206.161.15.5]) by hub.freebsd.org (Postfix) with ESMTP id DF6E537BC61 for ; Thu, 30 Mar 2000 06:52:14 -0800 (PST) (envelope-from tyson@stanfordalumni.org) Received: from stanfordalumni.org (tc1-s31.wizard.net [206.161.15.61]) by radagast.wizard.net (8.8.7/8.8.7) with ESMTP id JAA08782 for ; Thu, 30 Mar 2000 09:52:22 -0500 From: tyson@stanfordalumni.org Message-Id: <200003301452.JAA08782@radagast.wizard.net> To: freebsd-questions@freebsd.org Subject: Lynx forbidden MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <717.954427932.1@stanfordalumni.org> Date: Thu, 30 Mar 2000 09:52:12 -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I must be missing something obvious here. The LYNX port is marked ``forbidden'' because of its vulnerability to buffer overflow exploits; we have seen the security advisory, and the port's make file refuses to build. Why, then, is lynx still available for manual downloading from the ports collection? Or, more to the point, if it is still available for manual downloading, why disable the port's makefile mechanism at all? It seems to me that the better course would be to allow those who wish to go ahead and install it and take their chances. No, w3m isn't an alternative. It may be a great browser someday, but not yet. Don Tyson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message