←back to thread

Inverting the Xorshift128 random number generator

(littlemaninmyhead.wordpress.com)
108 points rurban | 1 comments | 31 Aug 25 18:49 UTC | HN request time: 0s | source
Show context
NooneAtAll3 ◴[04 Sep 25 13:02 UTC] No.45126799[source]▶
looking at the CVE report itself, Math.random() not being crypto-level seems to be known? - and vulnerability comes from Node.js using it for some crypto purpose

so OP simply did a good exercise for himself recreating exact weakness of it

replies(1): >>45126831 #
tptacek ◴[04 Sep 25 13:06 UTC] No.45126831[source]▶
No, the post takes the attack from 5 observations down to 3.
replies(1): >>45141945 #
NooneAtAll3 ◴[05 Sep 25 18:29 UTC] No.45141945[source]▶
no, the post takes a shoddy quickly-made implementation of an attack and improves it to its own better implementation of an attack

neither are professional frontline research, because said frontline work has already been done long loong ago when Xorshift was popularized and definitely when it became javascript's *default* rng

this is recreational cryptography, don't over-present it

replies(3): >>45143051 #>>45146945 #>>45148015 #
1. ScottContini ◴[06 Sep 25 10:07 UTC] No.45148015[source]▶
Also: I just realised who the person is that you were replying to, tptacek. Maybe you should Google his name. He's well known in cryptography, glad he is on my side! :-)