I added an addendum to the show notes for the #MilkSad episode, to explain that Mersenne Twister didn't become unsafe at some point: it was never designed to be used in cryptographic applications. But it's fine for its intended purposes (like Monte Carlo simulations).
https://podcast.sprovoost.nl/@nado/episodes/episode-83-the-milk-sad-vulnerability
If you find this stuff interesting, you should read (some of) the Serious Cryptography book: https://nostarch.com/seriouscrypto
It wouldn't hurt if cppreference.com would be more clear about this. Instead of "It produces high quality unsigned integer random numbers" , it should say "high quality, but not cryptographically secure, ".
https://en.cppreference.com/w/cpp/numeric/random/mersenne_twister_engine
It doesn't help that it links to a standards document which in its Requirements section mentions:
> "true" non-deterministic random numbers (for cryptography)
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1398.html
Only if you read the document carefully you'll learn why that requirement was pushed to the developer.
Just read this book recently, very recommended 🤙
