3 ms·
Somewhat related, I wrote a blog post about (P)RNGs a few years ago: http://dvt.name/2010/clock-drift-hardware-prng/ http://dvt.name/2010/clock-drift-hardware-p
by dvt 11y ago
Somewhat related, I wrote a blog post about (P)RNGs a few years ago: http://dvt.name/2010/clock-drift-hardware-prng/ http://dvt.name/2010/clock-drift-hardware-prng/. It's interesting to se V8 favor accuracy over speed.
I'd think that having a "secure" random number generator isn't that important of a deal given the fact that all code runs client-side anyway (so why the need for cryptographic security?).
- IgorPartola 11y agoSo in one application I have I use Math.random() as a fallback when window.crypto isn't available to generate UUID's. I am less concerned with security, and more concerned with collisions between different clients. Making Math.random() more uniform helps with that, though only marginally since browsers that did that also support window.crypto.
- zeta0134 11y agoThat's actually not always true. Any application running on node.js is using the V8 engine as it's serverside backend, and might thusly be affected. There are also a handful of applications that do clientside encryption. (MEGA comes to mind, someone here should chime in with a better example.) Just because the use case is uncommon doesn't make it invalid.