Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60902
Return-Path: <ircmaxell@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 37051 invoked from network); 20 Jun 2012 10:12:25 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 20 Jun 2012 10:12:25 -0000
Authentication-Results: pb1.pair.com header.from=ircmaxell@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=ircmaxell@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
X-PHP-List-Original-Sender: ircmaxell@gmail.com
X-Host-Fingerprint: 209.85.216.170 mail-qc0-f170.google.com  
Received: from [209.85.216.170] ([209.85.216.170:52209] helo=mail-qc0-f170.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id E9/C1-25489-802A1EF4 for <internals@lists.php.net>; Wed, 20 Jun 2012 06:12:24 -0400
Received: by qcmt36 with SMTP id t36so4733408qcm.29
        for <internals@lists.php.net>; Wed, 20 Jun 2012 03:12:21 -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;
        bh=k9Ff8nbmBSdrutU51m9gkttR4sZqtl0mvwniYxWyDpQ=;
        b=SMd8/K8jOOCgaU1Btpq5CSEvqfjSosxEyyh3QR19YnXwQvE7rvV1UJqfDZDgpffztO
         xMYR0MUUSH0ud7+6OCnjIM7mZcrApMLmzy/C4IV/r5dUbR5yrKU+GRgJFq/mPzhRCy1v
         zfQUj3YPifxZHtwjP3JO7tYLHPafj0a/hhJRXsEIDW5qmsnWJZ1eNs96R/N9XvsSK/Is
         gp6PlWPpQbK2rjXS23bZh5uV0B8IXybjohilE2D3HhG8H0D3/WAtgPIgoHT2JXrUE2Ww
         dRiIX78zhdpWJR6K2IfzH0Q37D7TvFNHfqPDiQkps35B+7T3ET+azx4WIwuVafXcofuc
         cR5w==
MIME-Version: 1.0
Received: by 10.224.39.75 with SMTP id f11mr39652240qae.70.1340187141592; Wed,
 20 Jun 2012 03:12:21 -0700 (PDT)
Received: by 10.229.232.11 with HTTP; Wed, 20 Jun 2012 03:12:21 -0700 (PDT)
In-Reply-To: <CAEZPtU4bnjS5_gA0PQT+3QhO0Sa09EZ6VE-2xzSJpJDsamDSaw@mail.gmail.com>
References: <CAAyV7nEw5uLC05dz+kqCrFtUJ9yOUeKvR6uZTGo8E6+TjYMoUA@mail.gmail.com>
	<CAEZPtU4bnjS5_gA0PQT+3QhO0Sa09EZ6VE-2xzSJpJDsamDSaw@mail.gmail.com>
Date: Wed, 20 Jun 2012 06:12:21 -0400
Message-ID: <CAAyV7nF7yKEuEimxtoiLb3u26bUTazN1Y4JVxAO5DaS2M0w4dw@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] [RFC] Add hash_pbkdf2 function
From: ircmaxell@gmail.com (Anthony Ferrara)

Pierre,

> Very nice work! Thanks :)

Thanks!

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

When you say "currently available algorithms", are you talking about
the hash library as a whole? Or recommended for use with PBKDF2? Or
other iterated stretching algorithms similar to PBKDF2?

> 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.

I'm not arguing that. When I proposed the draft earlier I had
indicated that it was for trunk, and others said it could go into 5.4.
That's why I put that section in the RFC. Personally, I'm in the
middle. I can see some advantage to adding it to 5.4, but I can also
see some disadvantages. So I leave that decision to others (such as
yourself).

Thanks,

Anthony