Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:16951 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 35182 invoked by uid 1010); 28 Jun 2005 04:04:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 35166 invoked from network); 28 Jun 2005 04:04:35 -0000 Received: from unknown (HELO crynwr.com) (127.0.0.1) by localhost with SMTP; 28 Jun 2005 04:04:35 -0000 X-Host-Fingerprint: 192.203.178.14 ns1.crynwr.com Linux 2.0.3x (1) Received: from ([192.203.178.14:1264] helo=ns1.crynwr.com) by pb1.pair.com (ecelerity 1.2 r(5656M)) with SMTP id 1C/39-00424-35CC0C24 for ; Tue, 28 Jun 2005 00:04:35 -0400 Received: (qmail 19098 invoked from network); 28 Jun 2005 04:04:31 -0000 Received: from dpc6745223014.direcpc.com (HELO desk.crynwr.com) (67.45.223.14) by pdam.crynwr.com with SMTP; 28 Jun 2005 04:04:31 -0000 Received: (qmail 15235 invoked by uid 500); 28 Jun 2005 03:35:51 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dog; d=crynwr.com; b=gLF1qiNXwnjXYyJ8UsKr6Pm8h7WzdlGPqdpnNFusp94JUjptWT4+dhZxaCyv9xfP ; MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17088.50583.728119.993938@desk.crynwr.com> Date: Mon, 27 Jun 2005 23:35:51 -0400 To: internals@lists.php.net In-Reply-To: References: <20050624055017.25065.qmail@desk.crynwr.com> <04.19.22648.2895CB24@pb1.pair.com> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid Subject: Re: [PHP-DEV] Re: 'include' Considered Harmful From: nelson@crynwr.com (Russell Nelson) Ron Korving writes: > Personally, I think include is just fine the way it is. Google for "php security flaw". Do you think *that's* fine the way it is? Clearly, the fact that you can turn this behavior off suggests that somebody has noticed that it's badly designed. Rather than say, as some people have, "Well, just turn it off if you don't like it" or "Well, program around it by checking your data" or "php isn't a babysitter", it would be better to fix the flaw in the language that requires the flag to turn off the misdesigned behavior. If the very first thing you have to do with a language feature is make sure that it doesn't function as designed (which is to execute hostile content with local privileges), then clearly the design of that feature is wrong. -- --My blog is at blog.russnelson.com | If you want to find Crynwr sells support for free software | PGPok | injustice in economic 521 Pleasant Valley Rd. | +1 315-323-1241 | affairs, look for the Potsdam, NY 13676-3213 | | hand of a legislator.