Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751088AbdCQPcn (ORCPT ); Fri, 17 Mar 2017 11:32:43 -0400 Received: from frisell.zx2c4.com ([192.95.5.64]:60345 "EHLO frisell.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751169AbdCQPci (ORCPT ); Fri, 17 Mar 2017 11:32:38 -0400 MIME-Version: 1.0 In-Reply-To: <2785457.pDyvZpZC2q@positron.chronox.de> References: <2785457.pDyvZpZC2q@positron.chronox.de> From: "Jason A. Donenfeld" Date: Fri, 17 Mar 2017 16:31:29 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [ANNOUNCE] /dev/random - a new approach (code for 4.11-rc1) To: =?UTF-8?Q?Stephan_M=C3=BCller?= Cc: LKML , Linux Crypto Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 419 Lines: 10 Hey Stephan, Have you considered submitting this without so many options? For example -- just unconditionally using ChaCha20 instead of the configurable crypto API functions? And either removing the FIPS140 compliance code, and either unconditionally including it, or just getting rid of it? And finally just making this a part of the kernel directly, instead of adding this as a standalone optional component? Jason