Closed agallant closed 9 years ago
Just to be clear, the exact nature of the issue is still a little mysterious - we already exposed crypto.getRandomValues (https://github.com/freedomjs/freedom-for-node/issues/13) in freedom-for-node, which in principle ought to be enough for random seeding. So the solution to this may not be as large as "use some node webcrypto polyfill", but rather "find the specific bit of scope/logic that is pointing at something undefined for some reason."
Working in node 0.10 (https://github.com/freedomjs/freedom-pgp-e2e/pull/20), filed an issue for 0.11 (https://github.com/freedomjs/freedom-pgp-e2e/issues/21).
There is a lack of WebCrypto/SubtleCrypto interface in nodejs, which end-to-end actually grabs for randomness seeding. Possible avenues: https://github.com/skjindal93/W3C-Cryptography-API-NodeJS (more context at http://www.defensivejs.com/webcrypto/) http://polycrypt.net/