From: Michael Buesch <mb@bu3sch.de>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hw_random: add quality categories
Date: Wed, 27 Jun 2007 14:52:10 +0200 [thread overview]
Message-ID: <200706271452.11036.mb@bu3sch.de> (raw)
In-Reply-To: <20070627031800.GJ11115@waste.org>
On Wednesday 27 June 2007 05:18:00 Matt Mackall wrote:
> On Tue, Jun 26, 2007 at 04:45:24PM +0200, Michael Buesch wrote:
> > On Tuesday 26 June 2007 16:32:37 Matt Mackall wrote:
> > > > No wait. You are missing the whole point of this
> > > > quality category.
> > > > The whole point of it is to prevent defaulting to a bad RNG, if
> > > > there's a bad and a good one in a machine.
> > > > Well, what's bad.
> > > > It's easy. HWRNGs like the one in bcm43xx are bad.
> > > > It's proprietary and nobody knows what it does (I guess
> > > > it gathers the entropy from the network or something
> > > > and hashes that in hardware).
> > > > So such a device would be QUAL_LOW.
> > >
> > > If it's gathering its entropy from the network, it is not a QUAL_LOW
> > > RNG because it is not a hardware random number generator at all!
> > >
> > > Such a device is QUAL_PSEUDO or QUAL_UNKNOWN. If it's known or
> > > suspected to be bogus, it should be so marked.
> >
> > No, it should not be marked pseudo. It _is_ a RNG in hardware.
>
> Again, if it's not using an underlying physical process that's
> unpredictable, it does not deserve to be called a real HWRNG. It's no
> better than the software PRNG in the kernel at that point.
>
> If you have a reasonable suspicion that this is the case with the BCM
> part, then you should so mark it.
Done so in the new patch.
> > No, that's not true. I explained the difference to you and it's even
> > explained in the kdoc help text. Re-read it, please.
> > HIGH is for seperate dedicated extension devices that you buy and
> > stick into your machine. So it would default to that, as you want
> > to use that by default (why would you otherwise stick it in).
>
> I do not believe there exist devices that deserve to be classified as
> "HIGH".
You still didn't understand what I am trying to explain.
Please look at my new patch. The "DEDICATED" type is what QUAL_HIGH
meant.
Again: It is _just_ for selecting a default policy of which RNG
to enable by default. It is _not_ about quality. (And so the QUAL_XXX
defines were misnamed).
--
Greetings Michael.
prev parent reply other threads:[~2007-06-27 12:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 13:55 [PATCH] hw_random: add quality categories Michael Buesch
2007-06-24 14:30 ` Alexey Dobriyan
2007-06-24 14:43 ` Michael Buesch
2007-06-25 23:21 ` Andrew Morton
2007-06-26 13:56 ` Michael Buesch
2007-06-26 3:13 ` Matt Mackall
2007-06-26 14:06 ` Henrique de Moraes Holschuh
2007-06-26 14:20 ` Michael Buesch
2007-06-27 2:00 ` Henrique de Moraes Holschuh
2007-06-27 12:58 ` Michael Buesch
2007-06-27 16:40 ` Henrique de Moraes Holschuh
2007-06-27 17:56 ` Michael Buesch
2007-06-28 7:57 ` Henrique de Moraes Holschuh
2007-06-26 14:12 ` Michael Buesch
2007-06-26 14:32 ` Matt Mackall
2007-06-26 14:45 ` Michael Buesch
2007-06-27 3:18 ` Matt Mackall
2007-06-27 12:52 ` Michael Buesch [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=200706271452.11036.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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