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?
2013/11/1 Tankred Hase <[email protected]> > Hi, > > > I tried wrapping the whole thing in a worker thread, but then it doesn't > have access to window.crypto > > This has been an issue for quite a while. I see two options: > > 1.) take the code that requires window.crypto.getRandomValues out of > the openpgp.js bundle and call this outside of the worker context. > Then pass the random value as a seed to a pure code inside the worker > context wher pure js RNG takes over. > > 2.) split openpgp.js into AMD modules and selectively load required > modules into worker threads. This has the same effect as 1.) but would > still allow building all AMD modules to as single js file if such > deployments are desired. > > The devel branch is currently using common.js modules that would > simply need tobe wrapped with AMD's define(function(require) { ... }); > > The problem is that the devel branch is currently being heavily > refactored as it is and I'm waiting to try this in a seperate branch > once we have a working state. > > Thoughts? > > Tankred > _______________________________________________ > > http://openpgpjs.org > Subscribe/unsubscribe: http://list.openpgpjs.org >
_______________________________________________ http://openpgpjs.org Subscribe/unsubscribe: http://list.openpgpjs.org
