Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:13593 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58256 invoked by uid 1010); 29 Oct 2004 09:30:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 58220 invoked from network); 29 Oct 2004 09:30:25 -0000 Received: from unknown (HELO malcolm.ailis.de) (217.115.149.166) by pb1.pair.com with SMTP; 29 Oct 2004 09:30:25 -0000 Received: (qmail 9862 invoked by uid 64014); 29 Oct 2004 09:31:41 -0000 Received: from unknown (HELO ?172.16.0.1?) (k@62.206.245.30) by malcolm.ailis.de with SMTP; 29 Oct 2004 09:31:40 -0000 Message-ID: <41820D0B.9060601@ailis.de> Date: Fri, 29 Oct 2004 11:27:39 +0200 User-Agent: Mozilla Thunderbird 0.8 (X11/20040926) X-Accept-Language: en-us, en MIME-Version: 1.0 To: internals@lists.php.net References: <41811956.4050405@caedmon.net> <20041029105149.3b150c7d.tony2001@phpclub.net> <24e5f3b704102901044714577f@mail.gmail.com> <4182029F.2040700@ailis.de> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS 0.3.12 Subject: Re: [PHP-DEV] curl_init() is bypassing safe_mode & open_basedir restrictions From: k-php-dev@ailis.de (Klaus Reimer) Derick Rethans wrote: > Myth: Safe mode makes a PHP installation safe. I never said this. > webserver, not of a scripting language and therefore we shall not put > hacks in extensions because libraries do not adhere to safe mode. If there IS a possibility to make safe-mode a little bit more secure why don't do it? The fopen command of the libc doesn't check for safe-mode, so PHP is doing it. The curl library does not check for safe-mode but in this case you don't want PHP to do the check? Extension or not, the PHP curl functions are part of PHP, it's not an unsupported PECL extension. > It's almost certain that one can never put all the necessary > checks in the extension anyway. That's absolutely clear. That's why PHP has the ability to disable functions which can't be secured for safe-mode. But if this argument leads to sporadic securing of PHP functions (like "Why should I secure this function even if it's possible? safe-mode can't be secure anyway...") then safe-mode seems to make no sense at all. -- Bye, K (FidoNet: 2:240/2188.18) [A735 47EC D87B 1F15 C1E9 53D3 AA03 6173 A723 E391] (Finger k@ailis.de to get public key)