Insecure random values should be opt-in

Right now, this module will automatically fall back to Math.random() in browser environments that don’t support CSPRNG use, essentially failing open.

To operate securely, it should instead fail hard with an error, and only allow falling back to an insecure random source if the developer explicitly indicates that this is acceptable.

[broofa]

I actually feel like this is a pretty legitimate request. Most devs aren’t aware of the security issues of less-than-crypto-quality PRNGs. Requiring them to opt-into the existing possibly-insecure behavior is probably a good thing.

… in the next major version, though.

Reopen?

[defunctzombie]

While I understand your point, I think the current behavior is more developer friendly and since this module isn’t even aiming for strong crypto I feel less strongly that this is a real problem.