Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261314AbUK0TmW (ORCPT ); Sat, 27 Nov 2004 14:42:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261316AbUK0TmW (ORCPT ); Sat, 27 Nov 2004 14:42:22 -0500 Received: from hermes.domdv.de ([193.102.202.1]:25099 "EHLO hermes.domdv.de") by vger.kernel.org with ESMTP id S261314AbUK0TmV (ORCPT ); Sat, 27 Nov 2004 14:42:21 -0500 Message-ID: <41A8D89B.9090909@domdv.de> Date: Sat, 27 Nov 2004 20:42:19 +0100 From: Andreas Steinmetz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040918 X-Accept-Language: en-us, en, de MIME-Version: 1.0 To: Jan Engelhardt CC: Javier Villavicencio , Linux Kernel Subject: Re: no entropy and no output at /dev/random (quick question) References: <41A7EDA1.5000609@migraciones.gov.ar> In-Reply-To: X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 849 Lines: 17 Jan Engelhardt wrote: > I doubt that timer and eth* are a non-predictable source. As such, they should > not contribute to the entropy. Better is the keyboard and/or mouse. SSH traffic > is network traffic, and if you send it to a network card, you can expect an > interrupt at