public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: henrique <henrique@cyclades.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with random.c and PPC
Date: Thu, 15 Aug 2002 12:25:56 -0600	[thread overview]
Message-ID: <20020815182556.GV9642@clusterfs.com> (raw)
In-Reply-To: <200208151514.51462.henrique@cyclades.com>

On Aug 15, 2002  15:14 +0000, henrique wrote:
> Hello !!!
> 
> I am trying to use a program (ipsec newhostkey) that uses the random device 
> provided by the linux-kernel. In a x86 machine the program works fine but 
> when I tried to run the program in a PPC machine it doesn't work.
> 
> Looking carefully I have discovered that the problem is in the driver 
> random.c. When the program tries to read any amount of data it locks and 
> never returns. It happens because the variable  "random_state->entropy_count" 
> is always zero, that is, any random number is generated at all !!!??.
> 
> Does anyone know anything about this problem ? Any sort of help is very 
> welcomed.

Maybe the PPC keyboard/mouse drivers do not add randomness?  You should
also get randomness from disk I/O.  If your PPC system is diskless,
mouseless, and keyboardless, there is also a patch for 2.4 which allows
you to get randomness from network card interrupts, which is good enough
for all but the most incredibly paranoid people.

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


  reply	other threads:[~2002-08-15 18:23 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-15 15:14 Problem with random.c and PPC henrique
2002-08-15 18:25 ` Andreas Dilger [this message]
2002-08-15 19:03   ` Tom Rini
2002-08-15 19:59     ` Andreas Dilger
2002-08-15 21:04       ` Tom Rini
2002-08-16  1:50         ` H. Peter Anvin
2002-08-16 16:33           ` Oliver Xymoron
2002-08-16 16:28         ` Oliver Xymoron
     [not found]           ` <20020816170126.GD26993@opus.bloom.county>
2002-08-16 17:15             ` Oliver Xymoron
  -- strict thread matches above, loose matches on Subject: below --
2002-08-15 16:10 henrique
2002-08-16 10:00 Jon Burgess
2002-08-16 19:52 ` Oliver Xymoron
2002-08-16 17:51   ` henrique
2002-08-16 21:21     ` Ruth Ivimey-Cook
2002-08-17  0:47       ` Oliver Xymoron
2002-08-17  0:45     ` Oliver Xymoron
2002-08-17  6:05       ` Andreas Dilger
2002-08-17  7:23         ` Oliver Xymoron
2002-08-17  9:09           ` Andreas Dilger
2002-08-17 16:56             ` Oliver Xymoron
2002-08-19  9:29           ` Marco Colombo
2002-08-19 14:02             ` Oliver Xymoron
2002-08-19 15:11               ` Marco Colombo
2002-08-19 15:29                 ` Oliver Xymoron
2002-08-19 16:20                   ` Marco Colombo
2002-08-19 16:33                     ` Oliver Xymoron
2002-08-19 20:23                       ` Marco Colombo
2002-08-22  3:16             ` David Wagner
2002-08-16 20:52   ` Chris Friesen
2002-08-17  0:29     ` Oliver Xymoron
2002-08-22  3:19     ` David Wagner
2002-08-22 15:40       ` Chris Friesen
2002-08-22 17:25       ` Remco Post

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020815182556.GV9642@clusterfs.com \
    --to=adilger@clusterfs.com \
    --cc=henrique@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox