Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68820 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85255 invoked from network); 1 Sep 2013 20:18:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 Sep 2013 20:18:41 -0000 Authentication-Results: pb1.pair.com smtp.mail=php@marc-bennewitz.de; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=php@marc-bennewitz.de; sender-id=unknown Received-SPF: error (pb1.pair.com: domain marc-bennewitz.de from 80.237.132.171 cause and error) X-PHP-List-Original-Sender: php@marc-bennewitz.de X-Host-Fingerprint: 80.237.132.171 wp164.webpack.hosteurope.de Received: from [80.237.132.171] ([80.237.132.171:53615] helo=wp164.webpack.hosteurope.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C3/86-55332-021A3225 for ; Sun, 01 Sep 2013 16:18:41 -0400 Received: from dslb-088-072-022-021.pools.arcor-ip.net ([88.72.22.21] helo=[192.168.178.27]); authenticated by wp164.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) id 1VGE6X-0000mt-4y; Sun, 01 Sep 2013 22:18:37 +0200 Message-ID: <5223A11C.9050803@marc-bennewitz.de> Date: Sun, 01 Sep 2013 22:18:36 +0200 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130803 Thunderbird/17.0.8 MIME-Version: 1.0 To: internals@lists.php.net References: <521E64B6.30703@marc-bennewitz.de> <521F37E5.5040203@gmail.com> <5220F973.5000000@marc-bennewitz.de> <001701cea5e7$e872d030$b9587090$@org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;php@marc-bennewitz.de;1378066721;c714c222; Subject: Re: [PHP-DEV] More powerful (and backward compatible) API of random number generator functions From: php@marc-bennewitz.de (Marc Bennewitz) Am 01.09.2013 15:12, schrieb Jakub Zelenka: > The whole proposal is a bit confusing for me. The combination of PRNG > algorithm (MT) with libraries (libc, OpenSSL, GMP) that implements one or > more PRNG algorithms just doesn't make sense to me. It doesn't say anything > about the speed and crypto strength of the algorithms. I think that much > better solution would be an extension that implements a couple of > algorithms. Then you could select what algorithm you want to use. The good > idea would be to have some reasonable default algorithm that would be used > if the user doesn't know anything about algorithms. This could be > implemented as an extension and if it's good enough then it could be > proposed as the core addition. Agree, libc, openssl etc. are not algorithms and the name should reflect the used algorithm not the name of the library. Implementing it as an extension is ok - but the proposal also was to have more possibilities without bc using the default build-in functions. Additionally it would be great to have one standard API other extension can attach it's own algorithm to. Marc