Re:Cracking random number generators (xoroshiro128+)
by hlieberman on Tuesday August 22, 2017 @09:41AM
(#15072247)
Yes. GP is mistaken here; this is novel work that is somewhat concerning -- mostly in how it might apply to other similarly state-based RNGs.
[ Parent
| on HN ]
Re:Cracking random number generators (xoroshiro128+)
by karanlyons on Tuesday August 22, 2017 @11:02AM
(#15073078)
I wouldn’t say this work is novel in the general case of “PRNGs are not CSPRNGs”. You can throw a constraint solver at most any PRNG and given sufficient output determine the state fairly easily. As a datapoint, doing this for xoroshiro took me half an hour: https://gist.github.com/karanlyons/805dbcc9e898dbd17e06f2627...
Re:Cracking random number generators (xoroshiro128+)
by anfractuosity on Tuesday August 22, 2017 @11:10AM
(#15073145)
Heh, that sounds cool. I'll save opening that link for later.
Re:Cracking random number generators (xoroshiro128+)
by karanlyons on Tuesday August 22, 2017 @11:13AM
(#15073171)
Don’t worry, it’s safe: I didn’t put the actual solver, just proof that I solved it. Wouldn’t want to spoil the fun for anyone else :)
Re:Cracking random number generators (xoroshiro128+)
by pbnjay on Tuesday August 22, 2017 @10:08AM
(#15072533)
I made no comment on the work done here, it is novel and concerning if you use the outputs for important things. My comment is that non-cryptographic random number generators should not be used for security-critical functions.
These functions are specifically built for speed, not security.