Re: Re: [RFC][VOTE] Session ID without hashing
| From: | Yasuo Ohgaki | Date: | Wed, 06 Jul 2016 01:51:48 +0000 |
| Subject: | Re: Re: [RFC][VOTE] Session ID without hashing | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94399@lists.php.net to get a copy of this message | ||
Hi Christoph,
On Wed, Jul 6, 2016 at 12:37 AM, Christoph Becker <cmbecker69@gmx.de> wrote:
> On 05.07.2016 at 16:32, Leigh wrote:
>
>> On 5 July 2016 at 04:02, Pierre Joye <pierre.php@gmail.com> wrote:
>>> We can argue about the provided pnrng being CS but it is not php's job to
>>> decide.
>>
>> I think we need to drop the concerns about exposing "RNG state".
>>
>> A reminder of what php_random_bytes looks at (in order):
>> * CryptGenRandom on Windows
>> * arc4random_buf on modern BSD (where ChaCha20 is used)
>> * Linux getrandom(2) syscall where available
>> * /dev/urandom where available
>> * Throws an exception if it cannot access one of the above
>
> Would that imply that in this latter case sessions couldn't be used
> anymore? What would be the fallback in that case? From a quick glance
> at the current PR there appears to be none!
It relies on php_random_bytes() defined in ext/standard/random.c
Current PHP does not build without decent PRNG. The patch uses
php_random_bytes() simply.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net