From: Stephan Mueller <smueller@chronox.de>
To: "Łukasz Stelmach" <l.stelmach@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
robh+dt@kernel.org, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Kukjin Kim <kgene@kernel.org>,
linux-crypto@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-kernel@vger.kernel.org, m.szyprowski@samsung.com,
b.zolnierkie@samsung.com
Subject: Re: [RFC] crypto: exynos - Icrease the priority of the driver
Date: Tue, 05 Dec 2017 14:48:35 +0100 [thread overview]
Message-ID: <2500626.C7ppcC6VU6@tauon.chronox.de> (raw)
In-Reply-To: <20171205124214.31263-1-l.stelmach@samsung.com>
Am Dienstag, 5. Dezember 2017, 13:42:14 CET schrieb Łukasz Stelmach:
Hi Łukasz,
> exynos-rng is one of many implementations of stdrng. With priority as
> low as 100 it isn't selected, if software implementations (DRBG) are
> available.
What about using 300? The reason is the following: in the normal case, the
software PRNGs have 100 (X9.31) and 200 (SP800-90A DRBG). Thus, in normal
case, the hardware takes precedence.
In FIPS mode, the DRBG prio is increased by 200. As in FIPS mode you must have
a DRBG and assuming that the hardware does not implement a DRBG, the software
DRBG should be used as otherwise you have a FIPS-problem.
Ciao
Stephan
prev parent reply other threads:[~2017-12-05 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171205124216eucas1p17f46fc23ea35f7f2fcacc49d88e40a15@eucas1p1.samsung.com>
2017-12-05 12:42 ` Łukasz Stelmach
2017-12-05 13:48 ` Stephan Mueller [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=2500626.C7ppcC6VU6@tauon.chronox.de \
--to=smueller@chronox.de \
--cc=b.zolnierkie@samsung.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=l.stelmach@samsung.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®