Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:73763 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56623 invoked from network); 22 Apr 2014 08:48:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Apr 2014 08:48:25 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.99 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.99 smtp99.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.99] ([108.166.43.99:53244] helo=smtp99.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D0/31-45364-7DC26535 for ; Tue, 22 Apr 2014 04:48:24 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id CBAF41B0CA3; Tue, 22 Apr 2014 04:48:20 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 760FB1B07F1; Tue, 22 Apr 2014 04:48:20 -0400 (EDT) Message-ID: <53562CD0.5070006@sugarcrm.com> Date: Tue, 22 Apr 2014 01:48:16 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Yasuo Ohgaki CC: PHP internals References: <52FF3BB7.8030408@lsces.co.uk> <52FF465E.4040400@lsces.co.uk> <5355A48D.7050600@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] utf-8 filenames in phar files. From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > e.g. Old browsers had _many_ security issues with ill-formed strings. > One valid example I can think of right now is filter evasion. > Another is DoS. Browsers may refuse to render page at all when there is > ill-formed > strings. e.g. Recent Chrome. Yet another is injections. i.e If user > assumes path name > encoding is UTF-8 and didn't escape, their program could be vulnerable > to injections. I'm sure these are serious issues, but I'm not sure - how do they relate to the phar fix we're talking about? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227