readelf | grep rand. There are NOT thousands of FOSS projects using rand where they need a csPRNG.
"Shiiiiiiit, that effect was cryptographic quality noise produced, not the deterministic sequence it was supposed to be."
-
-
LOL. Seriously, you saw that one happen, or are you talking out of your ass ?
-
Like, give me a specific CONCRETE filter you use in gimp that's affected by our non-deterministic random. Or it did not happen.
-
... actually, I'm going to expand on THAT. If you want a PRNG giving DETERMINISTIC RESULTS for something like gimp, you're definitely NOT GOING to want to use the libc rand(). ... Because it's not going to give you reproducible results from platform to platform.
-
Agreed. But for most users reproducibility on their own system sufficed. If sufficiently important on another you could LD_PRELOAD a replacement.
-
Bwahahaha Okay, so you admitted that predictable rand() is just a local convenience, and you're now advocating a dirty hack to make it portable. If you need reproducibility in a production setup, you shouldn't be using rand() anyway.
-
No, it makes it *possible* to reproduce the results you got once, even if a lot of work is involved. With csPRNG where it doesn't belong, it's impossible to ever reproduce.
-
Right. That's why we added *_deterministic versions. Better to have to explicitly ask for *deterministic versions than to have !csPRNG by default.
-
We have standards and specifications for a reason...
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.