Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93965
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.21 as permitted sender)
To: internals@lists.php.net, Leigh <leight@gmail.com>
References: <CAPwsocFZQdU2bt0OETeJMQYBXVUkK8ygB5jTb4ML3df4GZWdVA@mail.gmail.com>
 <e28227a3-d5b1-b971-3362-c6d31768aa44@fleshgrinder.com>
Message-ID: <dd126a62-a617-8f34-b3c6-8e7cd0df4674@gmx.de>
Date: Tue, 14 Jun 2016 20:14:31 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <e28227a3-d5b1-b971-3362-c6d31768aa44@fleshgrinder.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] RNG fixes
From: cmbecker69@gmx.de (Christoph Becker)

On 14.06.2016 at 19:45, Fleshgrinder wrote:

> On 6/14/2016 6:46 PM, Leigh wrote:
>> The issues I want to bring up for discussion are.
>>
>> * Replacing mt_rand() and rand() to a strong, modern RNG.
>> * Alternatively, fixing the current mt_rand() implementation to make it
>> standard
>> * Aliasing rand() to mt_rand() to improve output and cross-platform support
>> * Fixing RAND_RANGE for large ranges.
>> * Replacing insecure uses of php_rand() with php_random_bytes()
>> * Making the array_rand() algorithm more efficient
>>
>> The RFC can be found here: https://wiki.php.net/rfc/rng_fixes
> 
> Why do we need so many functions to get a random int anyways if we now
> have random_int()? I would like to see all of them deprecated and
> removed in PHP 8.0.

In my opinion, we need at least one random function which yields
reproducible values.

-- 
Christoph M. Becker