[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] error: qcrypto_random_bytes() tried to read from /dev/[

From: Peter Maydell
Subject: Re: [Qemu-devel] error: qcrypto_random_bytes() tried to read from /dev/[u]random, even on windows
Date: Mon, 24 Apr 2017 14:30:25 +0100

On 24 April 2017 at 13:50, Daniel P. Berrange <address@hidden> wrote:
> For subject line, better to describe the change made, rather than
> the problem.
> On Mon, Apr 24, 2017 at 02:17:56PM +0200, address@hidden wrote:
>> Now it calls CryptGenRandom() if is it compiled for windows.
>> It might be possible to save the cryptographic provider in between
>> invocations, e.g. by making it static -- I have no idea how computationally
>> intensive that operation actually is.
> I'd think most people should really just enable gnutls during build. This just
> has to provide a fallback that's good enough to be functional. If someone 
> really
> cares about performance of this fallback, they can send patches later....

What I think is more worrying is the suggestion in the CryptAcquireContext
docs that this might for instance prompt the user for a password to
decrypt keys. We definitely don't want to do that every time. In
fact we'd rather not do it at all.

Googling suggests that the approach used by web browsers is
to use the not-very-documented RtlGenRandom function:

That looks much simpler than trying to use the official crypto
APIs. (It's also what the MS C runtime library does to implement

-- PMM

reply via email to

[Prev in Thread] Current Thread [Next in Thread]