Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103428
MIME-Version: 1.0
References: <CAESVnVrkOSN=9n+3rhTM=9SxnDNB4Vov2MOjE5RPcJoLb8Ukxw@mail.gmail.com>
 <34d96db5-623b-8e88-4c0a-f1a6662efd58@gmx.de>
In-Reply-To: <34d96db5-623b-8e88-4c0a-f1a6662efd58@gmx.de>
Date: Tue, 6 Nov 2018 13:47:02 -0600
Message-ID: <CAESVnVqhsN=PQW9Z2ajqP=7_mzG4OCM--j+kaAuTZ+_GXD7RXw@mail.gmail.com>
To: Christoph Becker <cmbecker69@gmx.de>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Re: [RFC][VOTE] Password Digest Mechanism Registry
From: pollita@php.net (Sara Golemon)

On Tue, Nov 6, 2018 at 11:40 AM Christoph M. Becker <cmbecker69@gmx.de> wrote:
>
> On 06.11.2018 at 17:58, Sara Golemon wrote:
>
> > Reminder that this RFC is mostly non user facing, it just provides
> > mechanisms for extensions to register hashing handlers for the
> > password_*() functions.  The primary user-facing effect of this is
> > that password scheme identifiers have changed.  There is a secondary
> > question on the RFC to address the BC impact of this.
>
> If we overload password_hash() and password_needs_rehash() to also
> accept integers as $algo, shouldn't passing ints be deprecated right away?
>
I would take the deprecation notice as a given, but yeah I'll add that
to the text.

-Sara