From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH 0/4] random,x86,kvm: Add and use MSR_KVM_GET_RNG_SEED Date: Wed, 16 Jul 2014 09:10:27 +0200 Message-ID: <53C62563.6050106@redhat.com> References: <20140716064110.GV18167@minantech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andy Lutomirski , kvm@vger.kernel.org, "H. Peter Anvin" , "Theodore Ts'o" , linux-kernel@vger.kernel.org, Kees Cook , x86@kernel.org, Srivatsa Vaddagiri , Raghavendra K T To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:2225 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753334AbaGPHKm (ORCPT ); Wed, 16 Jul 2014 03:10:42 -0400 In-Reply-To: <20140716064110.GV18167@minantech.com> Sender: kvm-owner@vger.kernel.org List-ID: On 07/16/2014 08:41 AM, Gleb Natapov wrote: > On Tue, Jul 15, 2014 at 07:48:06PM -0700, Andy Lutomirski wrote: >> virtio-rng is both too complicated and insufficient for initial rng >> seeding. It's far too complicated to use for KASLR or any other >> early boot random number needs. It also provides /dev/random-style >> bits, which means that making guest boot wait for virtio-rng is >> unacceptably slow, and doing it asynchronously means that >> /dev/urandom might be predictable when userspace starts. >> >> This introduces a very simple synchronous mechanism to get >> /dev/urandom-style bits. > > Why can't you use RDRAND instruction for that? You mean using it directly? I think simply for the very same reasons as in c2557a303a ...