cloud-hypervisor/vendor/registry-40351f815f426200/rdrand
Samuel Ortiz d5f5648b37 vendor: Add vendored dependencies
We use cargo vendor to generate a .cargo/config file and the vendor
directory. Vendoring allows us to lock our dependencies and to modify
them easily from the top level Cargo.toml.

We vendor all dependencies, including the crates.io ones, which allows
for network isolated builds.

Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>
2019-06-04 17:51:52 +02:00
..
benches vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
src vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
.cargo-checksum.json vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
appveyor.yml vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
Cargo.toml vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
LICENSE vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00
README.mkd vendor: Add vendored dependencies 2019-06-04 17:51:52 +02:00

An implementation of random number generators based on rdrand and rdseed instructions.

The random number generators provided by this crate are fairly slow (the latency for these instructions is pretty high), but provide high quality random bits. Caveat is: neither AMDs nor Intels designs are public and therefore are not verifiable for lack of backdoors.

Unless you know what you are doing, use the random number generators provided by the rand crate (such as EntropyRng) instead.