Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268928AbUIXSn1 (ORCPT ); Fri, 24 Sep 2004 14:43:27 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269080AbUIXSn1 (ORCPT ); Fri, 24 Sep 2004 14:43:27 -0400 Received: from mx1.redhat.com ([66.187.233.31]:11427 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S268928AbUIXSnW (ORCPT ); Fri, 24 Sep 2004 14:43:22 -0400 Date: Fri, 24 Sep 2004 14:43:07 -0400 (EDT) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: "Theodore Ts'o" cc: Jean-Luc Cooke , , Subject: Re: [PROPOSAL/PATCH] Fortuna PRNG in /dev/random In-Reply-To: <20040924174301.GB20320@thunk.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 888 Lines: 26 On Fri, 24 Sep 2004, Theodore Ts'o wrote: > have *any* encryption algorithms in the kernel at all. As to whether > or not cryptoapi needs to be mandatory in the kernel, the question is > aside from /dev/random, do most people need to have crypto in the > kernel? If they're not using ipsec, or crypto loop devices, etc., > they might not want to have the crypto api in their kernel > unconditionally. As far as I know embedded folk do not want the crypto API to be mandatory, although I think Matt Mackall wanted to try and make something work (perhaps a subset just for /dev/random use). - James -- James Morris - 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/