linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Horia Geanta <horia.geanta@nxp.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	Aymen Sghaier <aymen.sghaier@nxp.com>,
	Vipul Kumar <vipul_kumar@mentor.com>,
	Chris Healy <cphealy@gmail.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Iuliana Prodan <iuliana.prodan@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v4 1/6] crypto: caam - RNG4 TRNG errata
Date: Mon, 25 Nov 2019 05:21:45 -0800	[thread overview]
Message-ID: <CAHQ1cqF_SW16_cvxpDmn6kYoLQDy7CBRfkftUs=u7gR8SQ=MTw@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0402MB348579B485FC139EDA222B0C984A0@VI1PR0402MB3485.eurprd04.prod.outlook.com>

On Mon, Nov 25, 2019 at 12:02 AM Horia Geanta <horia.geanta@nxp.com> wrote:
>
> On 11/21/2019 5:56 PM, Andrey Smirnov wrote:
> > The TRNG as used in RNG4, used in CAAM has a documentation issue. The
> I assume the "erratum" consists in RTMCTL[TRNG_ACC] bit
> not being documented, correct?
>
> Is there an ID of the erratum?
> Or at least do you know what parts / SoCs have incorrect documentation?
>
> > effect is that it is possible that the entropy used to instantiate the
> > DRBG may be old entropy, rather than newly generated entropy. There is
> > proper programming guidance, but it is not in the documentation.
> >
> Is the "programming guidance" public?
>

I don't know the answers to any of those questions. I am not the
original author of this change, just ported if from NXP tree because
it seemed important. More than happy to drop this if you think it's
bogus.

Thanks,
Andrey Smirnov

  reply	other threads:[~2019-11-25 13:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 15:55 [PATCH v4 0/6] enable CAAM's HWRNG as default Andrey Smirnov
2019-11-21 15:55 ` [PATCH v4 1/6] crypto: caam - RNG4 TRNG errata Andrey Smirnov
2019-11-25  8:02   ` Horia Geanta
2019-11-25 13:21     ` Andrey Smirnov [this message]
2019-11-26  7:44       ` Horia Geanta
2019-11-21 15:55 ` [PATCH v4 2/6] crypto: caam - enable prediction resistance in HRWNG Andrey Smirnov
2019-11-26  9:13   ` Horia Geanta
2019-11-21 15:55 ` [PATCH v4 3/6] crypto: caam - allocate RNG instantiation descriptor with GFP_DMA Andrey Smirnov
2019-11-21 15:55 ` [PATCH v4 4/6] crypto: caam - move RNG presence check into a shared function Andrey Smirnov
2019-11-21 15:55 ` [PATCH v4 5/6] crypto: caam - replace DRNG with TRNG for use with hw_random Andrey Smirnov
2019-11-21 15:55 ` [PATCH v4 6/6] crypto: caam - expose SEC4 DRNG via crypto RNG API Andrey Smirnov
2019-11-23 15:29 ` [PATCH v4 0/6] enable CAAM's HWRNG as default Chris Healy

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='CAHQ1cqF_SW16_cvxpDmn6kYoLQDy7CBRfkftUs=u7gR8SQ=MTw@mail.gmail.com' \
    --to=andrew.smirnov@gmail.com \
    --cc=aymen.sghaier@nxp.com \
    --cc=cphealy@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horia.geanta@nxp.com \
    --cc=iuliana.prodan@nxp.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vipul_kumar@mentor.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;
as well as URLs for NNTP newsgroup(s).