Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 18 Aug 2002 02:26:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 18 Aug 2002 02:26:55 -0400 Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com ([24.136.46.5]:50194 "EHLO svr-ganmtc-appserv-mgmt.ncf.coxexpress.com") by vger.kernel.org with ESMTP id ; Sun, 18 Aug 2002 02:26:55 -0400 Subject: Re: [PATCH] (0/4) Entropy accounting fixes From: Robert Love To: Linus Torvalds Cc: Oliver Xymoron , linux-kernel In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 18 Aug 2002 02:31:02 -0400 Message-Id: <1029652262.898.12.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 937 Lines: 22 On Sun, 2002-08-18 at 00:01, Linus Torvalds wrote: > So I think that if we just made the code be much less trusting (say, > consider the TSC information per interrupt to give only a single bit of > entropy, for example), and coupled that with making network devices always > be considered sources of entropy, we'd have a reasonable balance. I think that sounds good. I have a patch which I can send - it needs to be rediffed I suspect - that has each network device feed the entropy pool. (Actually, it creates a new flag, SA_NET_RANDOM, that defines to SA_SAMPLE_RANDOM or 0 depending on a configure setting. If you want it unconditional, that is just as easy though). Robert Love - 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/