From: Javier Villavicencio <javierv@migraciones.gov.ar>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: no entropy and no output at /dev/random (quick question)
Date: Mon, 29 Nov 2004 19:51:58 -0300 [thread overview]
Message-ID: <41ABA80E.5040005@migraciones.gov.ar> (raw)
In-Reply-To: <Pine.LNX.4.53.0411272019350.27610@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>I have a server that runs kernel 2.6.9, some web and monitoring
>>services, it's connected to two different networks with two different
>>network cards, and somehow a php developer discovered that /dev/random
>>wasn't giving any entropy to him (O_O) so i checked it out...
>>[...]
>>As you may see my only sources of entropy where the timer, eth0, eth1
>>and the DAC960.
>
>
> 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 <time>... prdictable.
>
>
> Jan Engelhardt
Hmm you got it wrong, I'm saying that my only "interrupt generating
hardware" was NOT contributing to the entropy. I mean, the timer (OF
COURSE NOT) and the NICs (same) but why don't the DAC960???
--
Javier Villavicencio
Administrador/Consultor
Direccion Nacional de Migraciones
Ministerio del Interior
Republica Argentina
prev parent reply other threads:[~2004-11-29 22:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 2:59 no entropy and no output at /dev/random (quick question) Javier Villavicencio
2004-11-27 4:38 ` Javier Villavicencio
2004-11-27 19:20 ` David Wagner
2004-11-28 6:29 ` Herbert Xu
2004-11-29 15:32 ` Theodore Ts'o
2004-11-30 12:49 ` Horst von Brand
2004-11-30 16:48 ` Javier Villavicencio
2005-01-07 19:17 ` Denis Vlasenko
2004-11-27 19:24 ` Jan Engelhardt
2004-11-27 19:22 ` Jan Engelhardt
2004-11-27 19:42 ` Andreas Steinmetz
2004-11-27 21:35 ` David Schwartz
2004-11-27 21:44 ` Jan Engelhardt
2004-11-29 22:47 ` Javier Villavicencio
2004-11-29 22:51 ` Javier Villavicencio [this message]
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=41ABA80E.5040005@migraciones.gov.ar \
--to=javierv@migraciones.gov.ar \
--cc=jengelh@linux01.gwdg.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.