From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
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 17:08:13 +0200 [thread overview]
Message-ID: <1147792093.983.26.camel@johannes> (raw)
In-Reply-To: <200605161658.33855.mb@bu3sch.de>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
On Tue, 2006-05-16 at 16:58 +0200, Michael Buesch wrote:
> 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).
I did, but no predictability tests, only FIPS 140-2 or so. It checked
out pretty well but someone claimed that the RNG was predictable because
it was probably only used for some of the coding for wireless. I don't
know how to test this hypothesis as I don't know enough about QAM and
whatever codings are used there (nor do I know where you'd need
(pseudo-)random numbers)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
prev parent reply other threads:[~2006-05-16 15:09 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
2006-05-16 15:08 ` Johannes Berg [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=1147792093.983.26.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=imipak@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--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