The C++ standard gives little guarantees for the quality of std::random_device. As I remember, MinGW on Windows uses the Mersenne Twister with a hardcoded seed for it.
boost::random_device, on the other hand, has better guarantees: it is only implemented where there's a decent entropy source.
Re:Linux /dev/urandom and concurrency
by mike-cardwell on Friday April 18, 2014 @06:28PM
(#7611662)
Thanks for the info. Seeing as I'm already using boost, that sounds very useful.
Please don't do this. This exact approach is what caused the problems described in the article.
If you need secure random numbers, do what you had above (though in light of other comments, perhaps consider a different algo besides MT).
[edit] I'm going to skip using the Mersenne twister engine and just use std::random_device for all random data, instead of as a seed. It seems on Linux at least that random_device is basically /dev/urandom. I assume the source will be sane on other OS's too.