Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261346AbUK0Vog (ORCPT ); Sat, 27 Nov 2004 16:44:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261343AbUK0Vog (ORCPT ); Sat, 27 Nov 2004 16:44:36 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:32705 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S261345AbUK0Vob (ORCPT ); Sat, 27 Nov 2004 16:44:31 -0500 Date: Sat, 27 Nov 2004 22:44:24 +0100 (MET) From: Jan Engelhardt cc: Linux Kernel Subject: RE: no entropy and no output at /dev/random (quick question) In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 987 Lines: 24 >> Timer, ok. But network - only if you are in full control of the network >> segment the system is attached to which may be the case for your private >> network but usually you can't predict what network traffic is actually >> going on. > > You would need a lot more than that to predict the TSC value when a packet >is received. All kinds of unpredictable elements get mixed in, such as the >offset between the network's timing source and the processor's as well as >the cache efficiency in getting the networking code running to the point >that it checks the TSC. Sounds like I started a hell of a discussion (again) :) Jan Engelhardt -- Gesellschaft für Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 Göttingen, www.gwdg.de - 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/