Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95330 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 77235 invoked from network); 20 Aug 2016 00:31:24 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Aug 2016 00:31:24 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:49898] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/11-03566-BD4A7B75 for ; Fri, 19 Aug 2016 20:31:23 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 9C8DD7830BC; Sat, 20 Aug 2016 02:31:18 +0200 (CEST) Received: from w530phpdev (pD9FD224E.dip0.t-ipconnect.de [217.253.34.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id E3D9A7830BC; Sat, 20 Aug 2016 02:31:15 +0200 (CEST) To: "'Davey Shafik'" , "'Christoph M. Becker'" Cc: References: <036401d1f30f$afa85a40$0ef90ec0$@belski.net> <3dc2f23a-c4fb-a63d-ab7f-fa841091b313@gmx.de> <53037294-e8ed-31c8-95ef-522e02333e7c@gmx.de> In-Reply-To: Date: Sat, 20 Aug 2016 02:31:11 +0200 Message-ID: <016101d1fa7a$298a5220$7c9ef660$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQJbEaE//F5lW0cR7swmVABvraDmAAJiu2+BAgfbgvkCjM4OdwKFaoYdAosRfQae3o9L4A== Content-Language: en-us Subject: RE: [PHP-DEV] SQLite 3.14 From: anatol.php@belski.net ("Anatol Belski") Hi Davey, > -----Original Message----- > From: Davey Shafik [mailto:davey@php.net] > Sent: Friday, August 19, 2016 7:09 PM > To: Christoph M. Becker > Cc: Anatol Belski ; internals@lists.php.net > Subject: Re: [PHP-DEV] SQLite 3.14 >=20 > Christophe, >=20 > I got the failure multiple times in my Debian Jessie docker container = that I use > for builds - you can check it out yourself at = https://github.com/dshafik/php-build > to see the setup. >=20 > Thanks for looking into this! >=20 > - Davey >=20 > On Sat, Aug 20, 2016 at 01:35 Christoph M. Becker > wrote: >=20 >=20 > Hi Davey! >=20 > On 19.08.2016 at 15:32, Davey Shafik wrote: >=20 > > I saw this failure while packaging 7.1.0beta3, and assume it might = be > > related to your update: > > > > FAIL SQLite3 open_basedir checks > > [ext/sqlite3/tests/sqlite3_21_security.phpt] > > > > =3D=3D=3D=3D=3D=3D=3D=3DDIFF=3D=3D=3D=3D=3D=3D=3D=3D > > 006- > > 007- Warning: SQLite3::__construct(): open_basedir restriction in > effect. > > File(%s) is not within the allowed path(s): (.) in > > %ssqlite3_21_security.php on line %d > > 008- Exception: open_basedir prohibits opening %s in > > %ssqlite3_21_security.php:%d > > 009- Stack trace: > > 010- #0 %ssqlite3_21_security.php(%d): SQLite3->__construct('%s') > > 011- #1 {main} > > =3D=3D=3D=3D=3D=3D=3D=3DDONE=3D=3D=3D=3D=3D=3D=3D=3D > > > > Can you please look into this in time for RC1? >=20 > I've just checked again with the tagged PHP-7.1.0beta3, but the test > succeeds on my machine. Therefore it's hard for me to assess what is > wrong. According to the diff, it appears that the second DB which > shouldn't be created according to the open_basedir restriction, is > actually successfully created. >=20 > Anyway, it's rather unlikely that an open_basedir related failure is > caused by updating SQLite, as this check is part of the PHP = binding[1], > which has not been affected by this commit. The issue might be = caused > by commit cc125f27[2], but that's also somewhat unlikely, because the > Travis checks usually succeed generally. >=20 > Can you reproduce the test failure? In which enviroment? >=20 > [1] /sqlite3.c#L125 7.1.0beta3/ext/sqlite3/sqlite3.c#L125> > > [2] >=20 I was checking this and saw no failure as well. From the test diff, it = doesn't look like a crash but something with that try/catch block. Maybe = there'll be more luck with a reproducer, if you could post the exact = command line? You can read it from the corresponding .sh file or just by = appending --verbose. Regards Anatol