Frequently Asked Questions
Registration is required to create a unique credential so unique entropy bits are sent to each user. We kept registration requirements to an absolute minimum, asking only for your name and email address, and we also offer the ease of use of registering with your LinkedIn or Twitter accounts.
All communication is secured with SSL and data in the user database is encrypted as well. The entropy stream is also sent over SSL and contains additional security safeguards built into the protocol.
Entropy is the statistical measure of disorder within a set of data, usually measured as a fraction of a bit-per-bit of data in the sample. An 8 bit number might contain 7.2 bits of effective entropy. But entropy is only part of the quest for randomness. Cryptography requires random numbers that are not just statistically random but also unpredictable. For example, the digits of the number Pi (3.1415926535897932384… etc.) may appear random and contain statistical entropy but are easily predicted.
Proving randomness requires knowledge of how the data was originally generated. Whitewood's True Random Number Generator (TRNG) uses a quantum property of light to generate perfectly random bits at 350 MBits per second. For more information on the generator please take a look at our white paper.
Whitewood's quantum-based True Random Number Generator (TRNG) is hosted in our data center, and generates many millions of truly random bits per second. Those bits are streamed over the network to our client driver/kernel module installed on your device. The bits are received by the client and then encrypted using a randomly generated rotating key before being placed in your OS entropy pool.
We do not record the bits that are sent out - we just don't have the space to do it! Furthermore, the raw network delivered entropy is combined with your existing other sources of entropy before being placed into the entropy pool, so the end result is not solely dependant on the bits send by our server.
The OS collects and distills entropy from real world events including keystrokes or mouse movement, system interrupt timing, timers inside the CPU - as well as other available third party sources such as special RNGs built into various computer chips, external devices, and more.
Not at all. Your current applications get their random numbers from the standard OS functions, which in turn get entropy from the same entropy pool where we mix in our entropy bits. By making the entropy pool more random we're improving the functioning of the OS's random number generators used by all applications so there is no need to change anything.
Sure! It's a great use case for supplementary entropy since there are more and more virtual machines able to run on less and less hardware, which creates a serious risk of entropy starvation.
Absolutely, as long as your cloud instance is running a supported Operating System.
The current service supports one client per customer. Contact us, we'd be happy to support your wider deployment needs.
The current service does not support saving entropy to a file or providing random data files. Contact us, we'd be happy to work with you as we have done with many others.
Currently we support 64 bit Linux: Ubuntu 14.04 or higher (or compatible) and CentOS 7+ (or compatible) and Windows 10 (64 bit), and other OSes and versions will follow. Contact us to submit a request for a specific OS or version or provide feedback about important OSes we should consider.