From owner-freebsd-questions Thu Mar 30 8:38:57 2000 Delivered-To: freebsd-questions@freebsd.org Received: from firehouse.net (spook.networkoperations.com [209.42.203.59]) by hub.freebsd.org (Postfix) with SMTP id 22E6A37BCFA for ; Thu, 30 Mar 2000 08:38:51 -0800 (PST) (envelope-from abc@firehouse.net) Received: (qmail 1151 invoked by uid 100); 30 Mar 2000 16:38:44 -0000 Date: Thu, 30 Mar 2000 11:38:44 -0500 From: Alan Clegg To: Benjamin Lutz Cc: freebsd-questions@freebsd.org Subject: Re: Lynx forbidden Message-ID: <20000330113843.A1103@laptop.firehouse.net> References: <200003301605.LAA20134@radagast.wizard.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" X-Mailer: Mutt 1.0.1i In-Reply-To: ; from benlutz@datacomm.ch on Thu, Mar 30, 2000 at 06:31:53PM +0200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Out of the ether, Benjamin Lutz spewed forth the following bitstream: > Well, I still have a question though: Why was Lynx marked "forbidden" > at all, leading to misunderstandings? Or the standard unix user > expected to be able to do this basic kind of "hacking"? The lynx port is marked forbidden due to security problems. There is no misunderstanding. If you want to open yourself (and your users) up to buffer overflows in the code, you are more than welcome. AlanC --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: aGe4ky7L6Bh6aLMVlar2tfwVHZmcWHXk iQA/AwUBOOODE/cyv/gweBpYEQJDxwCeOA9VKWD6ZSsZXHvb+XJobnFvX0wAn3v9 eeREHFbY8c9tQu4NxrRn8jEE =KF4V -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message