linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: Thoughts about the b43 RNG
Date: Fri, 9 Jan 2009 11:15:22 +0100	[thread overview]
Message-ID: <200901091115.22375.mb@bu3sch.de> (raw)
In-Reply-To: <1231464656.5715.33.camel@brick>

On Friday 09 January 2009 02:30:56 Harvey Harrison wrote:
> On Thu, 2009-01-08 at 17:28 -0800, Harvey Harrison wrote:
> > On Fri, 2009-01-09 at 02:11 +0100, Michael Buesch wrote:
> > > I was doing some random tests on the b43 hardware RNG.
> > > These are the results.
> > > 
> > > I patched the firmware to not access the RNG register anymore.
> > > The unpatched firmware does two things. It reads the RNG register to get random values
> > > and it writes 0 to the register every now and then for whatever reason.
> > > Both reads and writes were patched out during my test. So the driver was
> > > the only one accessing the RNG.
> > > 
> > > This is the result of reading a few bytes from the RNG with the patched fw:
> > 
> > > I'm not sure about this. There aren't any obvious patterns.
> > > But maybe I'm just blind. Does somebody else see some pattern or
> > > has some RNG test program to recognize such patterns?
> > > 
> > > So let's do another test. Let's modify the previous test to
> > > write 0xFFFF instead of 0:
> > > 
> > 
> > NIST has a pretty good test suite I think.
> 
> Packaged for debian as dieharder if you want the command-line version.

Thanks. I didn't know it was already packaged. So I'll certainly try it.

-- 
Greetings, Michael.

  reply	other threads:[~2009-01-09 10:16 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 [this message]
2009-01-09 14:00 ` Holger Schurig

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=200901091115.22375.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=harvey.harrison@gmail.com \
    --cc=linux-wireless@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 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).