From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Geert Martin Ijewski <gm.ijewski@web.de>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] crypto_gen_random() now also works on windows
Date: Tue, 25 Apr 2017 14:54:52 +0100 [thread overview]
Message-ID: <20170425135452.GI21129@redhat.com> (raw)
In-Reply-To: <a7cc0ade-e37f-0c06-afdb-dbcf69a72e6c@redhat.com>
On Tue, Apr 25, 2017 at 08:52:58AM -0500, Eric Blake wrote:
> On 04/25/2017 08:42 AM, Daniel P. Berrange wrote:
> > On Mon, Apr 24, 2017 at 07:51:49PM +0200, Geert Martin Ijewski wrote:
> >> 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 openeing neither file worked it errored
> >> out.
> >>
>
> >> +int qcrypto_random_init(Error **errp)
> >> +{
> >> +#ifdef _WIN32
> >> + if (!CryptAcquireContext(&hCryptProv, NULL, NULL, PROV_RSA_FULL,
> >> + CRYPT_SILENT | CRYPT_VERIFYCONTEXT)) {
> >> + error_setg_errno(errp, GetLastError(),
> >> + "Unable to create cryptographic provider");
> >
> > Unfortunately the return value of 'GetLastError()' isn't an errno
> > so we can't use error_setg_errno here.
> >
> > Just use error_setg, and report the error value with a '(code=%u)'
> > substitution at the end of the error message.
> >
>
> Or, use error_setg_win32(), which is designed for this purpose.
Oh nice, didn't know that existed !
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-04-25 13:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 17:51 [Qemu-devel] [PATCH v2] crypto_gen_random() now also works on windows Geert Martin Ijewski
2017-04-25 13:42 ` Daniel P. Berrange
2017-04-25 13:52 ` Eric Blake
2017-04-25 13:54 ` Daniel P. Berrange [this message]
2017-04-25 17:11 ` Geert Martin Ijewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170425135452.GI21129@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=gm.ijewski@web.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.