Resetting the Windows RNG

Question

According to this research, Windows seems to produce the same sequence of random numbers indefinitely when a process is kicked off before a VM snapshot is taken. This is a huge issue obviously when cloning VMs; the cloned VMs will all generate the same random numbers, which may compromise many different functions that rely on good randomness (key generation, etc).

If somehow someone were to reset the RNG or force it to collect entropy again from its sources, then this would be less of a problem. Is this theoretically possible? How might it be done?

Answer 1

This is going to depend on your environment. Snapshots, clones, and gold-copy images all cause issues simply because they're using identical entropy pools to generate RNG for the system. VMWare offers virtio drivers that allow entropy to refresh from the core kernel but I don't think this exists for Windows.

In this case, a reboot refreshes the entropy pool but also has the very small window of below entropy threshold potential issues your reference also discusses. This is easily prevented by NOT allowing RNG functions for OpenSSL or other Keygen needs until the system is fully booted.

3rd option and in my thoughts the proper alternative is to rely on an external hardware rng to refresh your entropy pool and then pull from that. That allows you:

• True Entropy sources to populate all of the PRNGS on each virtual
• The ability to monitor each clone's entropy pool and refresh when entropy thresholds are hit (filling back up to 4k)
• No worries that you're using duplicated entropy pools from all of the clone images

None if this is an issue unless you have a compliance requirement and/or have keygen needs that'll saturate each vm's entropy pool and really cause a potential for known number scenarios. In those instances, go hardware RNG.

TL;DR

• Given sufficent time, the entropy pool is stirred and this issue becomes moot
• If you're relying on Windows or Linux for real SSL needs, don't rely on kernel entropy pools and go with an approved NIST 800-90(A/B) method; hardware via API or custom programming
• Have your app refresh in Windows: https://msdn.microsoft.com/en-us/library/windows/desktop/aa379942(v=vs.85).aspx