Re: crypt() should raise error without 2nd parameter
On Wed, Aug 7, 2013 at 6:20 PM, Yasuo Ohgaki <[email protected]> wrote:
> Hi all,
>
> It seems there are 2 options for master branch when crypt()'s 2nd parameter
> is omitted.
>
> - raise E_DEPRECIATED that advice use of stronger salt or password_hash()
> and make 2nd parameter required for future release.
> - make crypt() use stronger default salt/hash w/o error
>
> Since password_hash() is supposed to do better job, first option seems
> better to me.
Deprecating it means it will be removed in the future.
Please leave the function alone. This should be solved with education,
not a gun to peoples head.
-Hannes
Thread (10 messages)