lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1210934981.6381.1.camel@johannes.berg>
Date:	Fri, 16 May 2008 12:49:41 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	virtualization@...ts.linux-foundation.org,
	Jeff Garzik <jeff@...zik.org>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	LKML <linux-kernel@...r.kernel.org>, "H. Anvin" <hpa@...or.com>
Subject: Re: [PATCH 2/2] lguest: virtio-rng support


> +
> +/* Our random number generator device reads from /dev/urandom into the Guest's
> + * input buffers.  The usual case is that the Guest doesn't want random numbers
> + * and so has no buffers although /dev/urandom is still readable, whereas
> + * console is the reverse.

Is it really a good idea to use the hosts /dev/urandom to fill the
guests /dev/random?

johannes

Download attachment "signature.asc" of type "application/pgp-signature" (829 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ