Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103427
To: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
References: <CAESVnVrkOSN=9n+3rhTM=9SxnDNB4Vov2MOjE5RPcJoLb8Ukxw@mail.gmail.com>
Message-ID: <34d96db5-623b-8e88-4c0a-f1a6662efd58@gmx.de>
Date: Tue, 6 Nov 2018 18:40:51 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.3.0
MIME-Version: 1.0
In-Reply-To: <CAESVnVrkOSN=9n+3rhTM=9SxnDNB4Vov2MOjE5RPcJoLb8Ukxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC][VOTE] Password Digest Mechanism Registry
From: cmbecker69@gmx.de ("Christoph M. Becker")

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?

-- 
Christoph M. Becker