linux-kernel - Re: [PATCH v4 1/6] crypto: caam

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AM0PR0402MB3476636E6BF1CAE4B80435F198450@AM0PR0402MB3476.eurprd04.prod.outlook.com>
Date:   Tue, 26 Nov 2019 07:44:15 +0000
From:   Horia Geanta <horia.geanta@....com>
To:     Andrey Smirnov <andrew.smirnov@...il.com>,
        Aymen Sghaier <aymen.sghaier@....com>
CC:     "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        Vipul Kumar <vipul_kumar@...tor.com>,
        Chris Healy <cphealy@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Iuliana Prodan <iuliana.prodan@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH v4 1/6] crypto: caam - RNG4 TRNG errata

On 11/25/2019 3:22 PM, Andrey Smirnov wrote:
> On Mon, Nov 25, 2019 at 12:02 AM Horia Geanta <horia.geanta@....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.
> 
The implementation is fine.
I am just trying to understand the commit message.

Maybe Aymen, as author, could help.
Otherwise I suggest rewriting it, i.e. drop the mention of an erratum
and just say what's the problem in the RNG initialization code.

Thanks,
Horia