Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40226
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.172 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references:x-google-sender-auth;
        b=lCZjY/pQNW6fwZxs5oaHXc2T7TojOH2iN5MrkYDDJeVfl7hU2BQT4xwkz2zWQKzU/0
         Go3nwCkWab5/E3W3FI4Cql6uVK15vhfHKYXeX61RpuB7U3IvSrKvNNzOIGgzYQjLX84W
         DvczZxRMgdOeMbRKMy4rTOS+7/FWiLddGXIhk=
Message-ID: <b5f7bf6c0809021933o1bf6d1c5mdf1665e4580279af@mail.gmail.com>
Date: Tue, 2 Sep 2008 22:33:27 -0400
Sender: david.coallier@gmail.com
To: "Scott MacVicar" <scott@macvicar.net>
Cc: "PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <B4142BDF-7319-4AB4-8274-376FAEE822CC@macvicar.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <B4142BDF-7319-4AB4-8274-376FAEE822CC@macvicar.net>
Subject: Re: [PHP-DEV] OpenSSL random pseudo bytes
From: davidc@php.net ("David Coallier")

2008/9/2 Scott MacVicar <scott@macvicar.net>:
> Hi All,
>
> Attached and uploaded [1] is a patch to add the OpenSSL random pseudo byte
> function, at the moment it will return FALSE if the bytes aren't considered
> cryptographically strong, I am however considering making this parameter
> controlled.
>
> Any objections to me applying this to 5.3?

I'd say that 5.3 should be a rather "stable" version and that if we
add features we should make sure they are rock solid now. Perhaps
adding the control (Parameter to control the security/cryptography
level) now would save time and would make it a thing less to look back
in the future.

What do you think?
-- 
Slan,
David