Better cryptographic security for Node.js

[TimothyGu]

Currently, the autoseed() function returns the following as randomly-generated seed:

    return [+new Date, GLOBAL, GLOBAL.navigator && GLOBAL.navigator.plugins,
            GLOBAL.screen, tostring(pool)];

This is nowhere near secure, probably even Math.random() is better than that when entropy is not enabled.

Node.js provides crypto.randomBytes() which is supposed to be "cryptographically strong pseudo-random." So why not add that as an option?

[ForbesLindesay]

Because this will never be cryptographically secure. Probably we should just remove autoseed entirely. There is no good reason to use seed-random with a random seed. The whole purpose is to have reproducible tests.