Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58988 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 56688 invoked from network); 17 Mar 2012 23:45:47 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Mar 2012 23:45:47 -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 67.192.241.183 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.183 smtp183.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.183] ([67.192.241.183:60647] helo=smtp183.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D8/43-43639-A22256F4 for ; Sat, 17 Mar 2012 18:45:47 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp18.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id C1A002681AE; Sat, 17 Mar 2012 19:45:43 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp18.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 73F432681A7; Sat, 17 Mar 2012 19:45:43 -0400 (EDT) Message-ID: <4F652226.4020101@sugarcrm.com> Date: Sat, 17 Mar 2012 16:45:42 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: Simon Schick CC: PHP Internals List References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Randomize hash-function in php From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I don't know much about hash-maps and internal php-stuff at all, but > they say that the fix provided in 5.3.9 (and 5.4.0) is more a > work-around than a fix ... This is true, it is a workaround in a meaning that the hash stays the same, but the fix prevents one from using excessive amounts of data that makes the hash unusable. > Would it be an option to provide a real fix in PHP 6.0? They got the Definitely. However doing this has some challenges. We're working on it. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227