Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Aug 2002 06:11:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Aug 2002 06:11:22 -0400 Received: from Morgoth.esiway.net ([193.194.16.157]:29198 "EHLO Morgoth.esiway.net") by vger.kernel.org with ESMTP id ; Mon, 19 Aug 2002 06:11:17 -0400 Date: Mon, 19 Aug 2002 12:15:07 +0200 (CEST) From: Marco Colombo To: "Theodore Ts'o" cc: Oliver Xymoron , Linus Torvalds , Robert Love , linux-kernel Subject: Re: [PATCH] (0/4) Entropy accounting fixes In-Reply-To: <20020819042141.GA26519@think.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: 1170 Lines: 26 On Mon, 19 Aug 2002, Theodore Ts'o wrote: [...] > P.S. /dev/urandom should probably also be changed to use an entirely > separate pool, which then periodically pulls a small amount of entropy > from the priamry pool as necessary. That would make /dev/urandom > slightly more dependent on the strength of SHA, while causing it to > not draw down as heavily on the entropy stored in /dev/random, which > would be a good thing. Shouldn't it be moved to userpace, instead? Pulling a small amount of entropy from /dev/random can be done in userspace, too. And the application could choose *how often* and *how many* bits to pull. The kernel can only make a choice which may be too much for an application (making it drain more entropy than it needs) or too little for another (forcing it to use /dev/random directly). Let the kernel implement the Real Thing only (/dev/random). /dev/urandom really belongs to userspace. .TM. - 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/