This RFC proposes adding a user-land API for an easy to use and reliable CSPRNG in PHP.
By default PHP does not provide an easy mechanism for accessing cryptographically strong random numbers in user-land. Users have a few options like openssl_random_pseudo_bytes(), mcrypt_create_iv() or directly opening /dev/*random devices to obtain high quality pseudo-random bytes, but unfortunately system support for these functions and extensions varies between platforms and each come with their own set of problems
mcrypt_create_iv() function has no dependency on MCrypt lib yet it requires the MCrypt extension to be installed before it can be used. Users are forced to include an entire library for no reason.openssl_random_pseudo_bytes() is provided by the OpenSSL lib. This function comes with a $crypto_strong the meaning of which may just confuse users./dev/urandom is OS-specific.
In addition users may attempt to generate their own streams of random bytes relying on rand() or mt_rand(), and this is something we absolutely want to avoid.
There should be a user-land API to easily return an arbitrary length of cryptographically secure pseudo-random bytes directly and work on any supported platform.
The initial proposal is to add two user-land functions that return the bytes as binary and integer. Arbitrary length strings of random bytes are important for salts, keys and initialisation vectors. Integers based on CS random are important for applications where unbiased results are critical (i.e. shuffling a Poker deck).
Signatures:
random_bytes(int length); random_int(int min, int max);
Examples:
$randomStr = random_bytes($length = 16); $randomInt = random_int($min = 0, $max = 127);
The sources of random used are as follows:
CryptGenRandom is used exclusivelyarc4random_buf() is used if it is available (generally BSD specific)/dev/arandom is used where available/dev/urandom is used where none of the above is available
Any user-land code that defines a random_bytes() or random_int() function would generate a fatal error, however it is likely that these functions provide the same or similar functionality as desired.
PHP 7
This RFC should not impact the SAPI's.
No existing extensions are affected.
Opcache is unaffected.
There would be no new constants.
There would be no new php.ini defaults.
This change does not affect any of the existing rand() or mt_rand() functionality.
The concepts from the RFC could be used to:
mcrypt_create_iv()session_id randomness generationThe current patch can be found here: https://github.com/php/php-src/pull/1119
The voting choices are yes (in favor for accepting this RFC for PHP 7) or no (against it).
Vote starts on March 14th, and will end two weeks later, on March 28th.
This RFC requires a 2/3 majority.
Big thanks to Anthony Ferrara, Daniel Lowrey, E. Smith and all the kids in the PHP room for all the help with this one!