Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 17 Aug 2002 23:47:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 17 Aug 2002 23:47:52 -0400 Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com ([24.136.46.5]:28176 "EHLO svr-ganmtc-appserv-mgmt.ncf.coxexpress.com") by vger.kernel.org with ESMTP id ; Sat, 17 Aug 2002 23:47:51 -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: 17 Aug 2002 23:51:52 -0400 Message-Id: <1029642713.863.2.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1265 Lines: 28 On Sat, 2002-08-17 at 23:05, Linus Torvalds wrote: > This is particularly true on things like embedded routers, where the > machine usually doesn't actually _run_ much user-level software, but is > just shuffling packets back and forth. Your logic seems to make it not add > any entropy from those packets, which can be _deadly_ if then the router > is also used for occasionally generating some random numbers for other > things. Agreed. Further, embedded routers - since they are headless/diskless - have problems even with the _current_ /dev/random code. They simply do not generate enough entropy to fulfill sshd requests [1]. Saying "use /dev/urandom" in this case means we may as well not have a /dev/random. There is a difference between incorrect accounting (which it seems you have identified) and just too strict gathering behavior. Robert Love [1] this is why I wrote my netdev-random patches. some machines just have to take the entropy from the network card... there is nothing else. - 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/