From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 16 Aug 2001 20:50:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 16 Aug 2001 20:49:34 -0400 Received: from odyssey.netrox.net ([204.253.4.3]:16308 "EHLO t-rex.netrox.net") by vger.kernel.org with ESMTP id ; Thu, 16 Aug 2001 20:48:21 -0400 Subject: Re: /dev/random in 2.4.6 From: Robert Love To: Andreas Dilger Cc: Steve Hill , "Richard B. Johnson" , linux-kernel@vger.kernel.org In-Reply-To: <20010816131112.V31114@turbolinux.com> In-Reply-To: <200108151713.f7FHDg0n013420@webber.adilger.int> <20010816131112.V31114@turbolinux.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12.99 (Preview Release) Date: 16 Aug 2001 20:49:01 -0400 Message-Id: <998009344.664.72.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 16 Aug 2001 13:11:12 -0600, Andreas Dilger wrote: > That said, there are still cases where network traffic _has_ to be enough > for /dev/random, given that some firewalls (e.g. LRP) can run from only > ramdisk, so have no other source of entropy than the network traffic. I put together a patch that addresses this, it allows the user to configure whether or not network devices contribute to the entropy pool. more information can be found -- Robert M. Love rml at ufl.edu rml at tech9.net