From: Stephan Mueller <smueller@chronox.de> To: Lukasz Stelmach <l.stelmach@samsung.com> Cc: Matt Mackall <mpm@selenic.com>, Herbert Xu <herbert@gondor.apana.org.au>, Arnd Bergmann <arnd@arndb.de>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Ray Jui <rjui@broadcom.com>, Scott Branden <sbranden@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Kukjin Kim <kgene@kernel.org>, Krzysztof Kozlowski <krzk@kernel.org>, Florian Fainelli <f.fainelli@gmail.com>, Markus Elfring <elfring@users.sourceforge.net>, Matthias Brugger <mbrugger@suse.com>, Stefan Wahren <wahrenst@gmx.net>, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> Subject: Re: [PATCH 1/2] hwrng: iproc-rng200 - Set the quality value Date: Fri, 15 May 2020 11:10:45 +0200 [thread overview] Message-ID: <3640422.T8yoyu11Ch@tauon.chronox.de> (raw) In-Reply-To: <dleftjimgx8tc3.fsf%l.stelmach@samsung.com> Am Freitag, 15. Mai 2020, 11:01:48 CEST schrieb Lukasz Stelmach: Hi Lukasz, As I mentioned, all that is or seems to be analyzed here is the quality of the cryptographic post-processing. Thus none of the data can be used for getting an idea of the entropy content. That said, the ent value indeed looks too low which seems to be an issue in the tool itself. Note, for an entropy assessment commonly at least 1 million traces from the raw noise source are needed. See for examples on how such entropy assessments are conducted in the LRNG documentation [1] or the Linux /dev/random implementation in [2] [1] appendix C of https://www.chronox.de/lrng/doc/lrng.pdf [2] chapter 6 of https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/ Publications/Studies/LinuxRNG/LinuxRNG_EN.pdf Ciao Stephan
WARNING: multiple messages have this Message-ID (diff)
From: Stephan Mueller <smueller@chronox.de> To: Lukasz Stelmach <l.stelmach@samsung.com> Cc: Florian Fainelli <f.fainelli@gmail.com>, Herbert Xu <herbert@gondor.apana.org.au>, Scott Branden <sbranden@broadcom.com>, Matthias Brugger <mbrugger@suse.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Matt Mackall <mpm@selenic.com>, linux-kernel@vger.kernel.org, Krzysztof Kozlowski <krzk@kernel.org>, linux-samsung-soc@vger.kernel.org, Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>, Kukjin Kim <kgene@kernel.org>, Arnd Bergmann <arnd@arndb.de>, Stefan Wahren <wahrenst@gmx.net>, Ray Jui <rjui@broadcom.com>, bcm-kernel-feedback-list@broadcom.com, Markus Elfring <elfring@users.sourceforge.net>, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org Subject: Re: [PATCH 1/2] hwrng: iproc-rng200 - Set the quality value Date: Fri, 15 May 2020 11:10:45 +0200 [thread overview] Message-ID: <3640422.T8yoyu11Ch@tauon.chronox.de> (raw) In-Reply-To: <dleftjimgx8tc3.fsf%l.stelmach@samsung.com> Am Freitag, 15. Mai 2020, 11:01:48 CEST schrieb Lukasz Stelmach: Hi Lukasz, As I mentioned, all that is or seems to be analyzed here is the quality of the cryptographic post-processing. Thus none of the data can be used for getting an idea of the entropy content. That said, the ent value indeed looks too low which seems to be an issue in the tool itself. Note, for an entropy assessment commonly at least 1 million traces from the raw noise source are needed. See for examples on how such entropy assessments are conducted in the LRNG documentation [1] or the Linux /dev/random implementation in [2] [1] appendix C of https://www.chronox.de/lrng/doc/lrng.pdf [2] chapter 6 of https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/ Publications/Studies/LinuxRNG/LinuxRNG_EN.pdf Ciao Stephan _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-15 9:11 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20200514190737eucas1p18ccdddb185ea7611683a6859e17bc721@eucas1p1.samsung.com> 2020-05-14 19:07 ` [PATCH 0/2] Set the quality value for two HW RNGs Łukasz Stelmach 2020-05-14 19:07 ` Łukasz Stelmach [not found] ` <CGME20200514190738eucas1p2695c0d8af064ee702209ca03696ef438@eucas1p2.samsung.com> 2020-05-14 19:07 ` [PATCH 1/2] hwrng: iproc-rng200 - Set the quality value Łukasz Stelmach 2020-05-14 19:07 ` Łukasz Stelmach 2020-05-14 20:20 ` Stephan Mueller 2020-05-14 20:20 ` Stephan Mueller [not found] ` <CGME20200514221852eucas1p2bea169d0b4467b0ec9e195c6ac58a08a@eucas1p2.samsung.com> 2020-05-14 22:18 ` Lukasz Stelmach 2020-05-14 22:18 ` Lukasz Stelmach 2020-05-15 8:32 ` Stephan Mueller 2020-05-15 8:32 ` Stephan Mueller [not found] ` <CGME20200515090647eucas1p21018edfd835730c9a68dcb186349ee74@eucas1p2.samsung.com> 2020-05-15 9:06 ` Lukasz Stelmach 2020-05-15 9:06 ` Lukasz Stelmach [not found] ` <CGME20200515090158eucas1p1b653fc50f1ad4f0f6c92525ab3188d45@eucas1p1.samsung.com> 2020-05-15 9:01 ` Lukasz Stelmach 2020-05-15 9:01 ` Lukasz Stelmach 2020-05-15 9:10 ` Stephan Mueller [this message] 2020-05-15 9:10 ` Stephan Mueller [not found] ` <CGME20200515110002eucas1p136759396d9b61f214d1f14856c009501@eucas1p1.samsung.com> 2020-05-15 10:59 ` Lukasz Stelmach 2020-05-15 10:59 ` Lukasz Stelmach [not found] ` <CGME20200514190740eucas1p293129b2ef3ba706652a9327e55db9649@eucas1p2.samsung.com> 2020-05-14 19:07 ` [PATCH 2/2] hwrng: exynos " Łukasz Stelmach 2020-05-14 19:07 ` Łukasz Stelmach 2020-05-14 20:20 ` Stephan Mueller 2020-05-14 20:20 ` Stephan Mueller [not found] ` <CGME20200519212617eucas1p1b6e7af0ecb894896b165601fafd6abe8@eucas1p1.samsung.com> 2020-05-19 21:25 ` [PATCH v2 0/2] Set the quality value for two HW RNGs Łukasz Stelmach 2020-05-19 21:25 ` Łukasz Stelmach [not found] ` <CGME20200519212619eucas1p22fa5d3db2521096dc4b79f6e53016d17@eucas1p2.samsung.com> 2020-05-19 21:25 ` [PATCH v2 1/2] hwrng: iproc-rng200 - Set the quality value Łukasz Stelmach 2020-05-19 21:25 ` Łukasz Stelmach 2020-05-20 6:23 ` Stephan Mueller 2020-05-20 6:23 ` Stephan Mueller [not found] ` <CGME20200520091043eucas1p15ecae108007382a95b01e42241cc7a26@eucas1p1.samsung.com> 2020-05-20 9:10 ` Lukasz Stelmach 2020-05-20 9:10 ` Lukasz Stelmach 2020-05-20 9:18 ` Stephan Mueller 2020-05-20 9:18 ` Stephan Mueller [not found] ` <CGME20200520104448eucas1p122e9a8ed84d5276a1b796e10ef5e1964@eucas1p1.samsung.com> 2020-05-20 10:44 ` Lukasz Stelmach 2020-05-20 10:44 ` Lukasz Stelmach 2020-05-20 11:53 ` Stephan Mueller 2020-05-20 11:53 ` Stephan Mueller 2020-05-20 12:00 ` Krzysztof Kozlowski 2020-05-20 12:00 ` Krzysztof Kozlowski 2020-05-20 12:11 ` Stephan Mueller 2020-05-20 12:11 ` Stephan Mueller [not found] ` <CGME20200520143211eucas1p21bd93be5c62726aa715db05bb6e7119b@eucas1p2.samsung.com> 2020-05-20 14:31 ` Lukasz Stelmach 2020-05-20 14:31 ` Lukasz Stelmach 2020-05-20 8:18 ` Kamil Konieczny 2020-05-20 8:18 ` Kamil Konieczny 2020-05-21 11:00 ` Stefan Wahren 2020-05-21 11:00 ` Stefan Wahren [not found] ` <CGME20200521191415eucas1p2d112a86171b23dcf255e7da53a56f4f3@eucas1p2.samsung.com> 2020-05-21 19:14 ` Lukasz Stelmach 2020-05-21 19:14 ` Lukasz Stelmach 2020-05-23 18:46 ` Stephan Müller 2020-05-23 18:46 ` Stephan Müller [not found] ` <CGME20200519212621eucas1p13279db41d930b69e115972463c994a37@eucas1p1.samsung.com> 2020-05-19 21:25 ` [PATCH v2 2/2] hwrng: exynos " Łukasz Stelmach 2020-05-19 21:25 ` Łukasz Stelmach
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=3640422.T8yoyu11Ch@tauon.chronox.de \ --to=smueller@chronox.de \ --cc=arnd@arndb.de \ --cc=b.zolnierkie@samsung.com \ --cc=bcm-kernel-feedback-list@broadcom.com \ --cc=elfring@users.sourceforge.net \ --cc=f.fainelli@gmail.com \ --cc=gregkh@linuxfoundation.org \ --cc=herbert@gondor.apana.org.au \ --cc=kgene@kernel.org \ --cc=krzk@kernel.org \ --cc=l.stelmach@samsung.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-samsung-soc@vger.kernel.org \ --cc=mbrugger@suse.com \ --cc=mpm@selenic.com \ --cc=rjui@broadcom.com \ --cc=sbranden@broadcom.com \ --cc=wahrenst@gmx.net \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.