Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40228
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.200.175 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=t5o14/YOb4q/OBK7WskwdW6ruCFA9Jdy3C6XdMHZP5Mq/3dJls66XublEPb/ajqXJt
         IPmmSmp+sFFgzAFxTfDyji8mNWw7iXevwY368ZqNfHlaAN/rSbnq6Vc7z0ZNf7wFTZX4
         kYRFz/XBK0+Xdnvez3lwDkvbj4M7q7KhQgKqY=
Message-ID: <b5f7bf6c0809022049t355751aau2a87282bbbe10f36@mail.gmail.com>
Date: Tue, 2 Sep 2008 23:49:02 -0400
Sender: david.coallier@gmail.com
To: "Scott MacVicar" <scott@macvicar.net>
Cc: "PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <175FE3A6-DF48-42A2-B206-9D2C42D9EAC5@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>
	 <b5f7bf6c0809021933o1bf6d1c5mdf1665e4580279af@mail.gmail.com>
	 <175FE3A6-DF48-42A2-B206-9D2C42D9EAC5@macvicar.net>
Subject: Re: [PHP-DEV] OpenSSL random pseudo bytes
From: davidc@php.net ("David Coallier")

>
> This function has been in OpenSSL for 8 years and supported by every version
> since 0.9.5. It's literally just exposing the API, it's safe for inclusion
> in 5.3 in my opinion.
>

I didn't express myself very clearly. What I meant is that we should
probably add that switch for the return right now instead of later
(IE: "I am however considering making this parameter controlled.")

I think it's safe to include it but I'll await on the RMs before
saying anything :) Exposing OpenSSL's API is a good idea imo.

--
Slan,
David