Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751832AbaGQRpp (ORCPT ); Thu, 17 Jul 2014 13:45:45 -0400 Received: from mail-lb0-f172.google.com ([209.85.217.172]:50394 "EHLO mail-lb0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750930AbaGQRpo (ORCPT ); Thu, 17 Jul 2014 13:45:44 -0400 MIME-Version: 1.0 In-Reply-To: References: <3e019617640d1b07d0ab1c9a91455957c201d4cd.1405546879.git.luto@amacapital.net> From: Andy Lutomirski Date: Thu, 17 Jul 2014 10:45:22 -0700 Message-ID: Subject: Re: [PATCH v3 1/5] x86,kvm: Add MSR_KVM_GET_RNG_SEED and a matching feature bit To: Andrew Honig Cc: kvm , "H. Peter Anvin" , "Theodore Ts'o" , "linux-kernel@vger.kernel.org" , Kees Cook , X86 ML , Daniel Borkmann , Srivatsa Vaddagiri , Raghavendra K T , Gleb Natapov , Paolo Bonzini , Bandan Das Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 17, 2014 at 10:43 AM, Andrew Honig wrote: >> + case MSR_KVM_GET_RNG_SEED: >> + get_random_bytes(&data, sizeof(data)); >> + break; > > Should this be rate limited in the interest of conserving randomness? > If there ever is an attack on the prng, this would create very > favorable conditions for an attacker to exploit it. IMO if the nonblocking pool has a weakness that requires us to conserve its output, then this is the least of our worries. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/