Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60898
Return-Path: <pierre.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 19652 invoked from network); 20 Jun 2012 06:38:07 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Jun 2012 06:38:07 -0000
Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.42 as permitted sender)
X-PHP-List-Original-Sender: pierre.php@gmail.com
X-Host-Fingerprint: 209.85.213.42 mail-yw0-f42.google.com  
Received: from [209.85.213.42] ([209.85.213.42:46673] helo=mail-yw0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 7C/A2-00136-ECF61EF4 for <internals@lists.php.net>; Wed, 20 Jun 2012 02:38:06 -0400
Received: by yhfq11 with SMTP id q11so6221128yhf.29
        for <internals@lists.php.net>; Tue, 19 Jun 2012 23:38:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        bh=yS4nMWegS3H9niJd1P1TI6Mw29GKKKWy6qDoJzMTK40=;
        b=zPlzTyiiBrdoxaGWxvmgFYLTzcmBXY8ZmFIDPkTNFd1tGLLmetwvBZew6G5iBTkZqd
         /p6SQmuJyGNxNEWi72dljgjO3Y6cloayPjZCaLtMB1OFGumWBaiU0i2eb4vR5numJLTy
         kGqXdSulNlW6j/wiUjwELg1GXrUjuo8Zme3RhH8cOVrByY7vq64YLrLdaKabKJuRpD7A
         KGB+ia2PVCZW5X5q0saKnfQjNobcg1+XQJBN5wi9c5nPwVXDEPPx8/Bijh0yOQpcjn01
         U3dMkDWUWA6paCj4W+TCkF0KrgEd+jZaJAE7aZtXv314jSSj1/RR5T9yN7LwOQogOHcA
         +FKw==
MIME-Version: 1.0
Received: by 10.236.114.161 with SMTP id c21mr26469206yhh.51.1340174283904;
 Tue, 19 Jun 2012 23:38:03 -0700 (PDT)
Received: by 10.147.113.7 with HTTP; Tue, 19 Jun 2012 23:38:03 -0700 (PDT)
In-Reply-To: <CAAyV7nEw5uLC05dz+kqCrFtUJ9yOUeKvR6uZTGo8E6+TjYMoUA@mail.gmail.com>
References: <CAAyV7nEw5uLC05dz+kqCrFtUJ9yOUeKvR6uZTGo8E6+TjYMoUA@mail.gmail.com>
Date: Wed, 20 Jun 2012 08:38:03 +0200
Message-ID: <CAEZPtU4bnjS5_gA0PQT+3QhO0Sa09EZ6VE-2xzSJpJDsamDSaw@mail.gmail.com>
To: Anthony Ferrara <ircmaxell@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] Add hash_pbkdf2 function
From: pierre.php@gmail.com (Pierre Joye)

hi Anthony!

On Tue, Jun 19, 2012 at 1:14 AM, Anthony Ferrara <ircmaxell@gmail.com> wrot=
e:
> Hello all,
>
> Since there wasn't that much traffic on the draft version of the RFC,
> I've moved it into Proposed.
>
> =A0https://wiki.php.net/rfc/hash_pbkdf2
>
> What are your thoughts?

Very nice work! Thanks :)

I would update the RFC with the current available algorithms or
recommended to be used (depending on the usage or goal).

About adding this to 5.4, I do not think it should be done. This is
not a small change and it may require more testing, both for the
implementations or the API (while it is fairly simple as of now :).
php-next is next year anyway.

Cheers,
--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org