Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:72378
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAHMUw2GOTY82_yxKLdqza8KrbHOSf11GF4Js_xz8jcjtejEmqA@mail.gmail.com>
References: <CAEZPtU7NJYRrsMMnNZZZ2fi_XSvqG5J=85=kd9yO5c54zfDCSw@mail.gmail.com>
	<CAHMUw2GOTY82_yxKLdqza8KrbHOSf11GF4Js_xz8jcjtejEmqA@mail.gmail.com>
Date: Fri, 7 Feb 2014 12:46:15 +0100
Message-ID: <CAEZPtU48fmeD9-cSZ8xwki3puEMDfSxJ+UJyixOfc3nj+TWpyA@mail.gmail.com>
To: Tjerk Meesters <tjerk.meesters@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] unify entropy source for all php related functions
From: pierre.php@gmail.com (Pierre Joye)

On Fri, Feb 7, 2014 at 12:42 PM, Tjerk Meesters
<tjerk.meesters@gmail.com> wrote:

> Here's a wild idea; assuming for a second that `rand()` is actually fed by a
> proper entropy source, are there BC implications if we did that? :)
>
> Alternatively, we would be looking at dedicated `random_` functions that
> provide a similar functionality and end up with an API such as:
>
> int random_integer($min, $max)
> string random_string($length, $crypto_safe)
>
> etc...

A good PRNG APIs will provides various weak implementations as well as
strong and crypto safe backend.

However, I would really try to only focus on the unification for the
entropy sources setting. We do not have the time to actually do a good
job/discussion/design about what would be a good PNRG APIs and
features, for 5.6.

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org