Re: Re: [RFC][DISCUSSION] Improve uniqid() uniqueness
| From: | Yasuo Ohgaki | Date: | Tue, 18 Oct 2016 07:35:58 +0000 |
| Subject: | Re: Re: [RFC][DISCUSSION] Improve uniqid() uniqueness | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-96413@lists.php.net to get a copy of this message | ||
On Tue, Oct 18, 2016 at 4:16 PM, Niklas Keller <me@kelunik.com> wrote:
> Yasuo Ohgaki <yohgaki@ohgaki.net> schrieb am Di., 18. Okt. 2016, 08:47:
>>
>> Hi Niklas,
>>
>> On Tue, Oct 18, 2016 at 3:36 PM, Niklas Keller <me@kelunik.com> wrote:
>> > Yasuo Ohgaki <yohgaki@ohgaki.net> schrieb am Di., 18. Okt. 2016, 02:21:
>> >>
>> >> Hi all,
>> >>
>> >> I committed this patch that simply use php_random_bytes() w/o any BC.
>> >
>> >
>> > Doesn't this throw now in some environments where /dev/urandom isn't
>> > readable?
>>
>> It could happen, but such system should not be used now a days.
>
>
> Sure, but it did happen that shared hosts block it, noticed during
> random_compat adoption.
>
> You claimed there isn't any BC break.
The line should be
"There is no BC for usable systems"
Any file permission could disturb PHP script execution, couldn't it?
I think it's nothing special for /dev/urandom. User should set up system
correctly to use PHP. Then there is no BC at all.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net