[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1748331.j7eDFAdTc1@tauon.chronox.de>
Date: Wed, 20 May 2020 08:23:59 +0200
From: Stephan Mueller <smueller@...onox.de>
To: Łukasz Stelmach <l.stelmach@...sung.com>
Cc: Matt Mackall <mpm@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Kukjin Kim <kgene@...nel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Markus Elfring <elfring@...rs.sourceforge.net>,
Matthias Brugger <mbrugger@...e.com>,
Stefan Wahren <wahrenst@....net>, linux-crypto@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org,
Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Subject: Re: [PATCH v2 1/2] hwrng: iproc-rng200 - Set the quality value
Am Dienstag, 19. Mai 2020, 23:25:51 CEST schrieb Łukasz Stelmach:
Hi Łukasz,
> The value was estimaded with ea_iid[1] using on 10485760 bytes read from
> the RNG via /dev/hwrng. The min-entropy value calculated using the most
> common value estimate (NIST SP 800-90P[2], section 6.3.1) was 7.964464.
I am sorry, but I think I did not make myself clear: testing random numbers
post-processing with the statistical tools does NOT give any idea about the
entropy rate. Thus, all that was calculated is the proper implementation of
the post-processing operation and not the actual noise source.
What needs to happen is that we need access to raw, unconditioned data from
the noise source that is analyzed with the statistical methods.
Ciao
Stephan
Powered by blists - more mailing lists