Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:58994 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81874 invoked from network); 18 Mar 2012 06:35:05 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 18 Mar 2012 06:35:05 -0000 Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.220.170 mail-vx0-f170.google.com Received: from [209.85.220.170] ([209.85.220.170:47768] helo=mail-vx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3D/81-63274-812856F4 for ; Sun, 18 Mar 2012 01:35:05 -0500 Received: by vcbfo14 with SMTP id fo14so6414457vcb.29 for ; Sat, 17 Mar 2012 23:35:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:from:in-reply-to:mime-version:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=NORcukvnirsOJDPVJmieAzArb4Zr3YBAIj/R2ahHwkk=; b=U2wb6Q5xMjHYgUBSXc6MDHPKzwzcTMALtAlGQRYfpNNQ1mIQgdHbGnTSQ0Db64qyDB dubthi1LnZAhvcIdL1pyVQGm+npXOCE1FCGnoJgMHYL5XhnCZOzqeJmNk7nvAmgcOMPS z+4pMQ6rNmnv+x7n/bmIOBz6NmK7gPKIwnJTFdV8G0JYBIJBJxISD4368HdVk1BBZcvi gHtC5NDRw3/v6XvbhOnFvSP2yhWsxaw0LmI5zpof5zNjBw+lqQhNFls8H20sI694PATQ /zSN3QvVUdEyL/bX11/22q1a8SNpSUL/qP72cIkjEwSBNLVrr6LDa6nreGHDlanUJBUG 528A== Received: by 10.52.27.1 with SMTP id p1mr4088180vdg.17.1332052501264; Sat, 17 Mar 2012 23:35:01 -0700 (PDT) References: <4F65267D.3040005@googlemail.com> <4F652868.7070901@sugarcrm.com> In-Reply-To: Mime-Version: 1.0 (1.0) Date: Sun, 18 Mar 2012 14:32:43 +0800 Message-ID: <4619201592745010989@unknownmsgid> To: Tjerk Anne Meesters Cc: Stas Malyshev , Sam , "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Randomize hash-function in php From: laruence@gmail.com (Xinchen Hui) Sent from my iPhone =E5=9C=A8 2012-3-18=EF=BC=8C13:57=EF=BC=8CTjerk Anne Meesters =E5=86=99=E9=81=93=EF=BC=9A > On Sun, Mar 18, 2012 at 8:12 AM, Stas Malyshev w= rote: >> Obvious solution would be to use a salt for the hash, which prevents bli= nd >> pre-computing of hash collisions. However, due to the fact that PHP hash >> values can be reused in different processes by bytecode caches, implemen= ting >> it properly is not trivial. > > What if php uses salts for specific hashes only, such as GPC (or all > hashes whose lifetime is limited to the current reuqest), and use a > zero-value salt for all others? definitely no=EF=BC=8Cthinking of pre-calculated hash. Or Ajax which use json_decode parse input json. IMO, this Make no sense but mess things up. Thanks > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >