Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95807
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ethreal.net designates 209.85.218.67 as permitted sender)
MIME-Version: 1.0
Sender: charlesportwoodii@ethreal.net
In-Reply-To: <8bd3a772-a4f1-6b1a-2421-87bedf17af7e@gmx.de>
References: <CAGC=tRnOVdBLrZUyYZJS3bNS6KKoHaCJn+wUrW8JLtUVBoa-7A@mail.gmail.com>
 <CAGC=tRn2YJicwhKpKdzpx55-Yk4Q9BohhQd7ktXa07j4MqL1DA@mail.gmail.com> <8bd3a772-a4f1-6b1a-2421-87bedf17af7e@gmx.de>
Date: Thu, 8 Sep 2016 12:42:28 -0500
Message-ID: <CAGC=tRmbQMaiS-GwigBYbw21qs-N9TobG3bWmj-7GdayPXeVDg@mail.gmail.com>
To: "Christoph M. Becker" <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11353910eb2d23053c028e9b
Subject: Re: [RFC][VOTE]: Argon2 Password Hash (Reopened)
From: charlesportwoodii@erianna.com ("Charles R. Portwood II")

--001a11353910eb2d23053c028e9b
Content-Type: text/plain; charset=UTF-8

On Thu, Sep 8, 2016 at 10:09 AM, Christoph M. Becker <cmbecker69@gmx.de>
wrote:

> On 08.09.2016 at 16:26, Charles R. Portwood II wrote:
>
> > On Wed, Aug 24, 2016 at 10:49 AM, Charles R. Portwood II wrote:
> >
> >> The RFC for introducing Argon2 as an alternative hashing algorithm for
> the
> >> password_* functions is now re-open. The RFC is available at
> >> https://wiki.php.net/rfc/argon2_password_hash
> >>
> >> Voting is open for 2 week, and will close on September 7th. A 50%+1
> >> majority required to pass. If you previously voted you will need to vote
> >> again, as the original vote was closed shortly after opening due to an
> >> issue with the original RFC language.
> >
> > Thanks to everyone who voted and contributed to the discussion. This RFC
> is
> > now closed, and was accepted 12-0 for 7.2. Would someone with VCS access
> > please merge this into master (7.2)?
>
> Thanks for the RFC and the PR.  I've just merged it (commit 1305fdaa).
>
> > Separately, what is the process for updating the manual since 7.2 is
> still
> > a ways off?
>
> Probably the first step should be to add some respective notes to
> php-src/UPRADING.  Do you want to make a PR or provide a patch by some
> other means?
>
> That would already be sufficient, as the doc team is supposed to
> integrate the UPGRADING information into the manual proper and the
> respective migration guide.
>
> Of course, it's also possible to update the manual now, making sure that
> there are notes about the availability (maybe as changelog entries).
>
> --
> Christoph M. Becker
>

Christoph,

I've provided a patch on the Github pull request for the UPGRADING notes..
https://github.com/php/php-src/pull/1997#issuecomment-245678319

--001a11353910eb2d23053c028e9b--