Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:72823 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72044 invoked from network); 26 Feb 2014 11:52:46 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Feb 2014 11:52:46 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.83 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 108.166.43.83 smtp83.ord1c.emailsrvr.com Linux 2.6 Received: from [108.166.43.83] ([108.166.43.83:32895] helo=smtp83.ord1c.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 36/D0-01653-C85DD035 for ; Wed, 26 Feb 2014 06:52:45 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 6E6A051C90; Wed, 26 Feb 2014 06:52:42 -0500 (EST) X-Virus-Scanned: OK Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id CC4B351715; Wed, 26 Feb 2014 06:52:41 -0500 (EST) Message-ID: <530DD588.1000407@sugarcrm.com> Date: Wed, 26 Feb 2014 13:52:40 +0200 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= CC: "internals@lists.php.net" References: <530C3C7B.8080907@sugarcrm.com> <530C77F8.2060809@sugarcrm.com> <1393328380.5233.45.camel@guybrush> In-Reply-To: <1393328380.5233.45.camel@guybrush> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Resolution for ver_export()/addslashes() encoding based script execution attack? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > The situation around var_export() is a bit more complicated. > var_export() is used to create application configuration, cache data > etc. so one might expect the PHP which created that to be able to read > that, again. Doing this isn't easy, though, as it makes the generated > file non-portable. Are you suggesting if var_export generates the data it may not be readable by standard PHP? Or by PHP running with specific script_encoding like SJIS? If the latter, I think var_export to generate valid SJIS data is hard to achieve, since SJIS is not ASCII-compatible. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227