On 4 September 2014 08:46, Aaron Toponce wrote:
> There are a couple things that you can do for older browsers that don't
> support
> crypto.getRandomValues():
>
> 1. You can build your own CSPRNG using either Blum Blum Shub or Blum
>Micali. In both cases, the CSPRNG is slow, and you'
On Mon, Jul 28, 2014 at 06:23:12PM +0200, Lodewijk andré de la porte wrote:
> I'm working on some Javascript client side crypto. There's a cryptographic
> quality random generator present in modern browsers, but not in older ones.
> I also don't trust browsers' random generators' quality.
>
> I'd
Not really. At minimum it's 2^128 bytes. But it's probably closer to 2^160.
On Thu, Sep 4, 2014 at 12:37 AM, Givon Zirkind wrote:
> forgive me for jumping into the middle of the conversation. but, if
> memory serves, such a scheme is limited to 2^128 bytes. then, the counter
> repeats. whic
