Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105887 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 78056 invoked from network); 13 Jun 2019 10:28:46 -0000 Received: from unknown (HELO mail-lj1-f175.google.com) (209.85.208.175) by pb1.pair.com with SMTP; 13 Jun 2019 10:28:46 -0000 Received: by mail-lj1-f175.google.com with SMTP id x25so12929151ljh.2 for ; Thu, 13 Jun 2019 00:41:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YaeInLQSBLQCI/X5Wik6w6qv9ZQriMivoobhE3XwZ0g=; b=nsqlSH1pDyjsCj4JghiYaKpVYyDGi5zG7B+paZT6rvBAlkVH7kTbPnYgZpIBGN1bn2 aw0cAVEe+66OTVoyS1M/dn9wZ1iV4oVKIC/e9banJJ+xlZzITx1RGS+9D+muHXY7c0L7 9+dox+6FwhrRixRxhuBZnU0dRLBme4nzFe4vgXA6mxzcO7XUSWm9K1+q4TLc8vqOlZeY R3lrplKlhA773B4AVlVIFXdhJvaN8CjlHQa6X6Luj4wV+DM0kzQcp3DFTQvDFVUlrzII i7MY3w7ngXBcwZO6VHQA3+nzUgcaROeiyO57H6UBuKyNDSNN84yQjDhmkuAE/+PzoT2z CaqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YaeInLQSBLQCI/X5Wik6w6qv9ZQriMivoobhE3XwZ0g=; b=T1FBAeHUE4Fxj0LTx8Jn0a5m5j4gk+6OX3vHG1oFtBXp0lZRaqf64LfDcVmJdnrwRY ssIQarcfaLMgbScDYf9WTVydgh+yGBXuhBZ4JODGoPD0jPXRFSGsQboZ1hrKB5Itl2kU nm7jPsf+OVCcVywVUJY8hudbojFyn0DEBiD5mE3QAGqdPLucSIQPfgvAqoOhR+EUfmgJ 4xWO0BlTotRKN54YCwhw85QCUszUHhXFAqQKC5uhM5OTpMfRuH0LYAQBR2Rw3xhHJOSH buQMBTX6+McBWySfFOaNYwBBEDHm9AoJb4lG8a7kGTlfAEk0ExbpR23Sqsxo7Rkc22xY H1/g== X-Gm-Message-State: APjAAAWPp+fqJVuGmHrgp9vOGVBOT/5154gTAK+uaR6KGk2gp0LUjN2V gZM2c+QUscfjnl1IAD2EZpxirWbNdTg7BwNjfvGNr9DA3zM= X-Google-Smtp-Source: APXvYqxAo9Dg/JpN8pYitMHNJFfMLVWAxfGYL7g6Kn4v+wir2qqCzkeAKpmtKYNeXD7MMTzLILOmObuet7j4cuggt50= X-Received: by 2002:a2e:6c07:: with SMTP id h7mr12327695ljc.177.1560411711036; Thu, 13 Jun 2019 00:41:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 13 Jun 2019 09:41:35 +0200 Message-ID: To: Lester Caine Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000bd6344058b2fa916" Subject: Re: [PHP-DEV] The real world ... From: nikita.ppv@gmail.com (Nikita Popov) --000000000000bd6344058b2fa916 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Jun 13, 2019 at 9:35 AM Lester Caine wrote: > Seen in the wild ... company name sanitised > > Warning: mysqli::mysqli(): (HY000/2002): No such file or directory in > /home/888/public_html/system/library/db/mysqli.php on line 7 > > Fatal error: Uncaught exception 'Exception' with message 'Error:
/>Error No: ' in /home/888/public_html/system/library/db/mysqli.php:10 > Stack trace: #0 > /home/888/public_html/system/nitro/core/nitro_db.php(29): > DB\MySQLi->__construct('localhost', '888_4y65f5...', > 'J?vJr+j5iCju-bo...', '888_4y65f5...', '3306') #1 > /home/888/public_html/system/nitro/core/nitro_db.php(13): > NitroDb->__construct('mysqli', 'localhost', '888_4y65f5...', > 'J?vJr+j5iCju-bo...', '888_4y65f5...', '3306') #2 > /home/888/public_html/system/storage/modification/system/library/db.php(1= 1): > > NitroDb::getInstanceWithParams('mysqli', 'localhost', '888_4y65f5...', > 'J?vJr+j5iCju-bo...', '888_4y65f5...', '3306') #3 > /home/888/public_html/system/framework.php(36): > DB->__construct('mysqli', 'localhost', '888_4y65f5...', > 'J?vJr+j5iCju-bo...', '888_4y65f5...', '3306') #4 > /home/888/public_html/vqmod/vqcache/vq2-system_startup.php(124): > require_once('/home/888 in > /home/888/public_html/system/library/db/mysqli.php on line 10 > =E4=BD=A0=E7=9A=84=E4=BB=A3=E7=A0=81=E5=87=BA=E9=94=99=E4=BA=86=EF=BC=9A > > I presume something has been updated that they have not been aware of > since it's library file that triggered the warning ... but it's not the > first time in recent years I've seen this sort of information on > commercial sites and while my own clients just get white screens, those > are created by the likes of Wordpress when 'automatic updates' happen. > > Many years ago the response was "well don't update", but 'current > practice' takes that out of OUR hands! So isn't it time that the > triggering exceptions like this did produce a more user secure response > to protect against leaks like this and provide a better alternative than > a white screen? > > In the case of this live site, I actually placed an order as it was only > some links that triggered the fault, which may explain why they were not > even aware there was a problem :( From the 'development' side, NitroDb-> > should obviously be handling the problem anyway. > display_errors=3DOff in production. Nikita --000000000000bd6344058b2fa916--