Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:74979
Return-Path: <yohgaki@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 56088 invoked from network); 18 Jun 2014 22:34:43 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 18 Jun 2014 22:34:43 -0000
Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.176 as permitted sender)
X-PHP-List-Original-Sender: yohgaki@gmail.com
X-Host-Fingerprint: 209.85.217.176 mail-lb0-f176.google.com  
Received: from [209.85.217.176] ([209.85.217.176:43736] helo=mail-lb0-f176.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id B0/81-46307-10412A35 for <internals@lists.php.net>; Wed, 18 Jun 2014 18:34:41 -0400
Received: by mail-lb0-f176.google.com with SMTP id w7so923971lbi.21
        for <internals@lists.php.net>; Wed, 18 Jun 2014 15:34:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type;
        bh=otY3Woe8ugDWRorY5BawR7riXebubFzpi/oogfY+G3w=;
        b=Ida95tj4IrjnEtJB7fITqfcH1KAIVaMlLEfXsMfUE7HZXh3cpfUwM14l3wzC2US823
         oSCnvDybb2Z7t3ZiJ13Qnm98OD1IwaRaKTgSQmY+4//TBggXYajCqigCshOCzRDjRrXo
         P4i4jVsgSj4iSgl3JNOa4VSfiBB5VsJeMtHWoZimzRVLXxk2a90zNcOq+fV6fvbQcSg+
         KCqgjXklM+heVTBtb2oh1X+KaRUNPr/pSAxISDbPZ/cHgCZ6Yr9z+D1KxB5C67ehdvpA
         xLmrRtK462xdRAQNU1Lw2++4i3VQxShXj/nnSptyLjO9VCm43QlnGFfscQj692VWZaVK
         heAg==
X-Received: by 10.152.170.193 with SMTP id ao1mr545956lac.27.1403130878069;
 Wed, 18 Jun 2014 15:34:38 -0700 (PDT)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
Received: by 10.112.14.9 with HTTP; Wed, 18 Jun 2014 15:33:57 -0700 (PDT)
In-Reply-To: <CALtuQzDC6qA=hXNC42MFEU3bHyKtNOB07LHQY4yeH22p5Vvy3Q@mail.gmail.com>
References: <CAEZPtU7rc+JpguO=Ke8UmiLLaidvyJEQ81C9Lsvn8yHgkp=+qw@mail.gmail.com>
 <53A00AC1.2050001@lsces.co.uk> <CALtuQzDC6qA=hXNC42MFEU3bHyKtNOB07LHQY4yeH22p5Vvy3Q@mail.gmail.com>
Date: Thu, 19 Jun 2014 07:33:57 +0900
X-Google-Sender-Auth: kWM4kjCo-XKbV65nuEX9yiCpxJw
Message-ID: <CAGa2bXYjAco7ymU5oAvLy=X51jzdhVpDr7EmkcOKgpBb37Cziw@mail.gmail.com>
To: Sebastian Krebs <krebs.seb@gmail.com>
Cc: Lester Caine <lester@lsces.co.uk>, PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0115e8708f908a04fc23dd62
Subject: Re: [PHP-DEV] PHP6, drop open_basedir?
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--089e0115e8708f908a04fc23dd62
Content-Type: text/plain; charset=UTF-8

Hi all,

On Tue, Jun 17, 2014 at 6:34 PM, Sebastian Krebs <krebs.seb@gmail.com>
wrote:

> In my experiene it only leads to a false sense of security. I've seen it
> more than once, that people just set a value there and believed, that they
> are now safe. On the other hand they wonder, why many things were broken,
> so they loosen the restrictions again.
>

I agree that many users do not understand what it does and what it's for.

It's a fail safe feature that should not be trusted.
open_basedir should not be trusted, but it does not mean
it's useless just like antivirus softwares. Security features
do not have to be perfect to be useful.

I'm -1 for removing open_basedir.
If there are users who misunderstand what it's for, we
should improve our documentation. IMHO.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--089e0115e8708f908a04fc23dd62--