From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>, Mark Brown <broonie@kernel.org>,
Will Deacon <will@kernel.org>, "Saidi, Ali" <alisaidi@amazon.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: RNDR/SS vs. SMCCC
Date: Thu, 03 Jun 2021 11:41:47 +1000 [thread overview]
Message-ID: <03af6cf4f263f9de4b7dbcf16e8a1c4962347191.camel@kernel.crashing.org> (raw)
In-Reply-To: <20210603011922.1d0e9249@slackpad.fritz.box>
On Thu, 2021-06-03 at 01:19 +0100, Andre Przywara wrote:
>
> You mean like this?
> https://gitlab.arm.com/linux-arm/linux-ap/-/commit/87e3722f437f9c3f09397e0e9812e6509c94786a
Yes. We have a similar one in Amazon Linux which I think Ali submitted
a while back but never went upstream.
> This is not reviewed nor widely tested, but I used it for assessing the
> quality of the SMCCC provided numbers on the Juno board using rngtest.
> I think one problem was that this opens the SMCCC to userland, so the
> entropy could be depleted from there (again under the assumption that
> this is really a problem in practice).
IMHO, userland can always adjust permission to /dev/hwrng if it wishes
to do so...
> I would be interested to hear opinions on this.
The issue is with things like FIPS certification (and other such
horrors) where I believe /dev/random is much harder to deal with since
it mixes multiple entropy sources.
Cheers,
Ben.
_______________________________________________
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:[~2021-06-03 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 23:54 RNDR/SS vs. SMCCC Benjamin Herrenschmidt
2021-05-27 12:50 ` Mark Brown
2021-05-27 23:12 ` Benjamin Herrenschmidt
2021-05-28 12:56 ` Mark Brown
2021-05-29 2:36 ` Benjamin Herrenschmidt
2021-05-31 1:02 ` Andre Przywara
2021-05-31 5:24 ` Ard Biesheuvel
2021-06-02 22:04 ` Benjamin Herrenschmidt
2021-06-03 0:19 ` Andre Przywara
2021-06-03 1:41 ` Benjamin Herrenschmidt [this message]
2021-06-03 7:10 ` Ard Biesheuvel
2021-06-03 21:30 ` Benjamin Herrenschmidt
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=03af6cf4f263f9de4b7dbcf16e8a1c4962347191.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=alisaidi@amazon.com \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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).