Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67677 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 87692 invoked from network); 10 Jun 2013 12:31:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jun 2013 12:31:36 -0000 Authentication-Results: pb1.pair.com smtp.mail=johannes@schlueters.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=johannes@schlueters.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error) X-PHP-List-Original-Sender: johannes@schlueters.de X-Host-Fingerprint: 217.114.211.66 config.schlueters.de Received: from [217.114.211.66] ([217.114.211.66:59232] helo=config.schlueters.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BE/2C-30264-827C5B15 for ; Mon, 10 Jun 2013 08:31:36 -0400 Received: from [192.168.2.20] (ppp-188-174-56-31.dynamic.mnet-online.de [188.174.56.31]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by config.schlueters.de (Postfix) with ESMTPSA id 6B0E265B0D; Mon, 10 Jun 2013 14:31:33 +0200 (CEST) To: Etienne Kneuss Cc: Pierre Joye , Stas Malyshev , Anatol Belski , Gustavo Lopes , Derick Rethans , PHP internals In-Reply-To: References: <6dd0f0c5be06dc0713890f2000a0b551.squirrel@webmail.klapt.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 10 Jun 2013 14:33:27 +0200 Message-ID: <1370867607.2374.115.camel@guybrush> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Re: #53437 From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mon, 2013-06-10 at 14:07 +0200, Etienne Kneuss wrote: > I propose we fix the serialization/unserialization crash in a way that > does not affect var_dump. That was the summary of my message a while back, too. Aside from that I trust the assessment of extension maintainers. I want to take this opportunity to remind everybody how close to EOL 5.3 is, though: PHP 5.3 is 26 point releases old and according to https://wiki.php.net/rfc/php53eol 5.3 will go to security only once 5.5 comes out, which might be by next month or so. Changing behavior so late in the game is bad, even if it is a small change only. johannes