From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Cc: Michael Buesch <mb@bu3sch.de>, bcm43xx-dev@lists.berlios.de
Subject: Re: Thoughts about the b43 RNG
Date: Fri, 9 Jan 2009 15:00:04 +0100 [thread overview]
Message-ID: <200901091500.04173.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <200901090211.03937.mb@bu3sch.de>
> I was doing some random tests on the b43 hardware RNG.
> These are the results.
As you're german, you should get a look at the current c't
2/2009. At page 172 it has a in-depth articel about randomness
tests. They also have some tools to download, see
http://von-und-fuer-lau.de/random-tools.html
http://www.heise.de/ct/09/02/links/172.shtml
prev parent reply other threads:[~2009-01-09 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 1:11 Thoughts about the b43 RNG Michael Buesch
2009-01-09 1:28 ` Harvey Harrison
2009-01-09 1:30 ` Harvey Harrison
2009-01-09 10:15 ` Michael Buesch
2009-01-09 14:00 ` Holger Schurig [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=200901091500.04173.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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;
as well as URLs for NNTP newsgroup(s).