diff options
| author | Geert Martin Ijewski | 2017-04-26 00:15:01 +0200 |
|---|---|---|
| committer | Daniel P. Berrange | 2017-05-09 15:41:47 +0200 |
| commit | a37278169d0d7d33270c6817f4a2e4f7345e1098 (patch) | |
| tree | e3f7866ae58d6dad3b84240cca0fe7852124e04b /linux-user | |
| parent | crypto: move 'opaque' parameter to (nearly) the end of parameter list (diff) | |
| download | qemu-a37278169d0d7d33270c6817f4a2e4f7345e1098.tar.gz qemu-a37278169d0d7d33270c6817f4a2e4f7345e1098.tar.xz qemu-a37278169d0d7d33270c6817f4a2e4f7345e1098.zip | |
crypto: qcrypto_random_bytes() now works on windows w/o any other crypto libs
If no crypto library is included in the build, QEMU uses
qcrypto_random_bytes() to generate random data. That function tried to open
/dev/urandom or /dev/random and if opening both files failed it errored out.
Those files obviously do not exist on windows, so there the code uses
CryptGenRandom().
Furthermore there was some refactoring and a new function
qcrypto_random_init() was introduced. If a proper crypto library (gnutls or
libgcrypt) is included in the build, this function does nothing. If neither
is included it initializes the (platform specific) handles that are used by
qcrypto_random_bytes().
Either:
* a handle to /dev/urandom | /dev/random on unix like systems
* a handle to a cryptographic service provider on windows
Signed-off-by: Geert Martin Ijewski <gm.ijewski@web.de>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Diffstat (limited to 'linux-user')
0 files changed, 0 insertions, 0 deletions
