Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95865
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Yasuo Ohgaki <yohgaki@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <CAGa2bXaM8q0mwhkz+XL6jbBaVLHDZ_-Jfj0aOPUq+te=fV=wow@mail.gmail.com>
Message-ID: <4e558dd2-b5e3-8091-68ae-578bed7aba88@gmx.de>
Date: Fri, 9 Sep 2016 15:56:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAGa2bXaM8q0mwhkz+XL6jbBaVLHDZ_-Jfj0aOPUq+te=fV=wow@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [RFC] Make uniqid() more unique
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 09.09.2016 at 07:12, Yasuo Ohgaki wrote:

> We all know, uniqid() is not unique at all and not safe as random ID
> at all. This would be one of the most misused function because of its
> name.

uniqid() yields truly unique values for a single machine (except for
CYGWIN, and potentially older Windows versions), if $more_entropy is
FALSE[1].  Of course, the function shouldn't be used for any crypto
purposes, but it is fine to get a unique ID if you have no database that
delivers a sequential index number (aka. autoincrement field), for instance.

[1]
<https://github.com/php/php-src/blob/PHP-7.0.11/ext/standard/uniqid.c#L68>

-- 
Christoph M. Becker