From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752232AbdBIJGF (ORCPT ); Thu, 9 Feb 2017 04:06:05 -0500 Received: from mail-pg0-f67.google.com ([74.125.83.67]:33389 "EHLO mail-pg0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752212AbdBIJGB (ORCPT ); Thu, 9 Feb 2017 04:06:01 -0500 Date: Thu, 9 Feb 2017 02:04:32 -0700 From: Alden Tondettar To: Greg Kroah-Hartman Cc: "Theodore Ts'o" , Arnd Bergmann , linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] random: Don't overwrite CRNG state in crng_initialize() Message-ID: <20170209090432.GA18039@rincewind> References: <1486611086-2290-1-git-send-email-alden.tondettar@gmail.com> <20170209064725.GA4363@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170209064725.GA4363@kroah.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 09, 2017 at 07:47:25AM +0100, Greg Kroah-Hartman wrote: > On Wed, Feb 08, 2017 at 08:31:26PM -0700, Alden Tondettar wrote: > > In short, the situation is: > > > > A) No usable hardware RNG or arch_get_random() (or we don't trust it...) > > Wait, why would you not trust arch_get_random()? Is it broken somehow > on some arches? If so, why not fix that as well? arch_get_random() makes use of RDRAND and similar CPU features. Some people do not wish to trust black-box RNG implementations. Alden