Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83819
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <54ED5811.10403@garfieldtech.com>
References: <CALYT1YrHA=E13eqzKnLSPSATdxRy_201yVDp-cdPurQeSkBhrQ@mail.gmail.com>
	<CAEZPtU6ZZ1MuoRvZooBgRmxQQ4p5jGFmUoVURwLfgVWhTqpkUg@mail.gmail.com>
	<CAPwsocH6HHVFYAycO-ZFnTKJzW1J8nuRS-x115ttY=wP0eukAg@mail.gmail.com>
	<CAEZPtU5EQO07tPSazwHbpqF38PdUMNyZhAQoiZ+ejvhnFDcKsg@mail.gmail.com>
	<CAAyV7nHE_Y-H-m5sgZTM=q-MKDXg0ycitTN+--0bPBQcSd8T2g@mail.gmail.com>
	<CALwr1G=BqkNrcxmG8DxRoHPo-US_eY=CrBVY7jeY_0Ekzao02g@mail.gmail.com>
	<CAAyV7nF8YGzDVTccWUSowVzD0=p1eF7e3NLC=zRO0CXiD8nc=w@mail.gmail.com>
	<CAGa2bXbtvkX9ZHgCEho=Mr1u_eHA-jfutReWOtKU957vJ=PxUQ@mail.gmail.com>
	<CALwr1G=1GccGAheuegDSznM-DTi=AfzjudgSoCi5JoKkMQK7mg@mail.gmail.com>
	<CAGa2bXbVu-r6AWuyN-1WAR9g3-TWZHLnC3ksBaFejHoSWhsGxw@mail.gmail.com>
	<54ED5811.10403@garfieldtech.com>
Date: Wed, 25 Feb 2015 20:02:15 +0000
Message-ID: <CALwr1G=6f1y+=SRxe_DqtG18bR17KXMzk33M1R=mfTGh-KgEig@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] [RFC] [DISCUSSION] Reliable user-land CSPRNG
From: padraic.brady@gmail.com (=?UTF-8?Q?P=C3=A1draic_Brady?=)

Hi Larry,

I think we'd be biting off too much to be worth chewing for other
character sets. Most uses are going to revolve around characters
allowed in URLs. Expanding that, to a degree, perhaps per a additional
character list, or character list flag, might not be too far, but
things will get interesting once you start requiring whole custom
character lists with multibyte chars thrown in.

Of course, random_string(LOTS_OF_FLAGS) might not be all that helpful
once you get enough variations involved to require a page of
explanatory text to cover them.

Paddy

On 25 February 2015 at 05:05, Larry Garfield <larry@garfieldtech.com> wrote=
:
> I can see the use for random_string(), but what about character sets?  Do=
es
> it only generate random characters within ASCCI / low-UTF-8?  Wouldn't
> someone in Novsibirsk want it to generate a random Cyrillic string?
>
> That said, I am +1 on the original proposal.  It's in the similar vein as
> password_hash(): If users have to think, they'll screw up. Don't make the=
m
> think.
>
> --Larry Garfield


--
P=C3=A1draic Brady

http://blog.astrumfutura.com
http://www.survivethedeepend.com