Thanks, well I decided not to change the random generation method. I've managed to solve my problem by counting how many random octets are needed for key generation at various bitlengths, so now I can pass an array of random octets to the worker thread at the beginning. The worker then gets its random octets from this array.
2013/11/2 Tankred Hase <[email protected]> > > So what you're saying in 1.) is have a JS pseudorandom generator that > always uses one real random number as seed? Wouldn't this be less secure > than generating n different real random numbers? > > All random numbers in a digital system are never really random. > They're just hard to guess/predict... which is good enough for > crypto. If you seed a good PRNG with enough entropy you should be > fine. > _______________________________________________ > > http://openpgpjs.org > Subscribe/unsubscribe: http://list.openpgpjs.org >
_______________________________________________ http://openpgpjs.org Subscribe/unsubscribe: http://list.openpgpjs.org
