From: Michael Buesch <mb@bu3sch.de>
To: Kyle Moffett <mrmacman_g4@mac.com>,
Johannes Berg <johannes@sipsolutions.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jonathan Day <imipak@yahoo.com>,
linux-kernel@vger.kernel.org, Zvika Gutterman <zvi@safend.com>,
Muli Ben-Yehuda <muli@il.ibm.com>
Subject: Re: /dev/random on Linux
Date: Tue, 16 May 2006 16:58:33 +0200 [thread overview]
Message-ID: <200605161658.33855.mb@bu3sch.de> (raw)
In-Reply-To: <B2E79864-3AC6-4B72-B97B-222FEDA136A1@mac.com>
On Tuesday 16 May 2006 10:15, you wrote:
> >> I would dismiss 2.2 for the cases of things like Knoppix because
> >> CDs introduce significant randomness because each time you boot
> >> the CD is subtly differently positioned. The OpenWRT case seems
> >> more credible.
I think most (all?) of the machines, OpenWRT runs on, are running
a bcm43xx wireless chip. This chip has a hardware random number
generator. patches to utilize it recently went into -mm.
But I must admit, we don't know how it generates random numbers.
But someone did some RNG tests on it in the past (I think it was
Johannes).
next prev parent reply other threads:[~2006-05-16 14:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:39 /dev/random on Linux Jonathan Day
2006-05-15 22:41 ` Alan Cox
2006-05-16 2:50 ` Muli Ben-Yehuda
2006-05-16 8:15 ` Kyle Moffett
2006-05-16 8:28 ` Muli Ben-Yehuda
2006-05-16 8:52 ` Kyle Moffett
2006-05-16 13:54 ` Zvi Gutterman
2006-05-16 20:17 ` Theodore Tso
2006-05-16 20:37 ` Chase Venters
2006-05-17 21:32 ` Theodore Tso
2006-05-16 10:24 ` Alan Cox
2006-05-16 12:46 ` Pavel Machek
2006-05-16 15:04 ` Christopher Friesen
2006-05-16 14:58 ` Michael Buesch [this message]
2006-05-16 15:08 ` Johannes Berg
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=200605161658.33855.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=imipak@yahoo.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=muli@il.ibm.com \
--cc=zvi@safend.com \
/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