Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:70223 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 3926 invoked from network); 20 Nov 2013 10:22:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Nov 2013 10:22:13 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-la0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:57380] helo=mail-la0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DF/33-20870-35D8C825 for ; Wed, 20 Nov 2013 05:22:12 -0500 Received: by mail-la0-f42.google.com with SMTP id ec20so7232728lab.29 for ; Wed, 20 Nov 2013 02:22:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KPffquHPUqht1SbYYFHMjjOjsvz7JwKsgz0BGScmy/A=; b=IDQmroDxYJAlCESZD5vmkmcxMHbx8nW1W9myXsweMlUhP+dxMETBhgKZEcyJptwHdG AEnQVrpb8XA5T0LK/1H3+EVmBUIt5pNzUsV5HHCiGSf5HvL2rKFU3ZWij6lKikYVMA44 j2vAWf8lCtUL+F/BMl23IvbzpG/GuegzBFWt8eC9u4fH1NHsMTCI412eIoPmq7OSNQ1k BqiOtaZBa3WjlwLsXl/FqdD11HoVSyVKH5gLbSkWwe5PyNITXeDMQYRNF6t7xhSHzYxA C5UHgpVClJ22gUuhEJNaBT1CbJeRd9rb7RwkMmo/YWiuvdU41VOKq8u0FiQdd0GJ/kzX LVpw== MIME-Version: 1.0 X-Received: by 10.152.234.170 with SMTP id uf10mr242038lac.43.1384942928622; Wed, 20 Nov 2013 02:22:08 -0800 (PST) Received: by 10.112.157.33 with HTTP; Wed, 20 Nov 2013 02:22:08 -0800 (PST) In-Reply-To: References: Date: Wed, 20 Nov 2013 11:22:08 +0100 Message-ID: To: Sebastian Krebs Cc: Michael Wallner , Richard Quadling , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Allowing [SAPI=] entries in ini files. From: pierre.php@gmail.com (Pierre Joye) On Wed, Nov 20, 2013 at 11:06 AM, Sebastian Krebs wrote: > 2013/11/20 Michael Wallner > >> On 19 November 2013 19:51, Sebastian Krebs wrote: >> >> > Just my 2 cents, but that sounds more like an issue with your >> > provider/hoster and not with PHP. I always thought of the additional >> > php.ini as a way to change some details and not a way to set up the whole >> > runtime. Especially when a user has write access to that file it seems to >> > me also an security issue, when PHP allows to set/change critical >> settings >> > there. >> >> You totally miss the point, Sebastian. As Richard already explained in >> his example, he as access to the ini-scan-dir, so he could set >> whatever setting he wants, just not SAPI-specific, but for all SAPIs. >> > > OK, but that doesn't change my opinion, that this in the hosters > responsibility, what he provides and what not. INI sections allow one to customize directories settings and having this feature to do some other settings based on the SAPI looks like a good complement. Obviously shared hosted applications are not the target for such features as they usually do not have access to php.ini but .htacess or .user.ini only. Cheers, -- Pierre @pierrejoye | http://www.libgd.org