From: Javier Villavicencio <javierv@migraciones.gov.ar>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: David Wagner <daw-usenet@taverner.cs.berkeley.edu>,
linux-kernel@vger.kernel.org
Subject: Re: no entropy and no output at /dev/random (quick question)
Date: Tue, 30 Nov 2004 13:48:27 -0300 [thread overview]
Message-ID: <41ACA45B.206@migraciones.gov.ar> (raw)
In-Reply-To: <200411301249.iAUCnJgs004281@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
> daw@taverner.cs.berkeley.edu (David Wagner) said:
>
>>Javier Villavicencio wrote:
>>
>>>it's encouraged to use /dev/urandom instead of /dev/random?
>
>
>>Yes, for almost all purposes, applications should use /dev/urandom,
>>not /dev/random. (The names for these devices are unfortunate.)
>
>
> To seed a random number generator, never directly.
>
>
>>Sadly, many applications fail to follow these rules, and consequently
>>/dev/random's entropy pool often ends up getting depleted much faster
>>than it has to be.
>
>
> Reading /dev/urandom depletes exactly the same pool, it just doesn't block
> when the pool is empty. As said pool has other uses, indiscriminate reading
> of either can DoS other parts of the system.
But why if /dev/random depletes and you don't have any source of entropy
? As you may have seen in my setup I had no mouse/keyboard attached to
that server, and the only "things" capable of generate entropy where the
two nics and the DAC960.
So I've enabled entropy only for the local nic and the DAC960 (at least
"I think", for the dac :+) and now I'm plenty of entropy, but for a
setup like this, the server may have been running without entropy at all
for weeks (I've forgot to check the uptime :+P).
About this, think about php generating session_id()s without entropy
(o_O), and stuff like that....
Salu2.
Javier Villavicencio.
next prev parent reply other threads:[~2004-11-30 16:49 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 [this message]
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
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=41ACA45B.206@migraciones.gov.ar \
--to=javierv@migraciones.gov.ar \
--cc=daw-usenet@taverner.cs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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