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] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB34850724B851235EE1FCE2D0987C0@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Date:   Tue, 19 Feb 2019 06:57:10 +0000
From:   Horia Geanta <horia.geanta@....com>
To:     Philipp Puschmann <philipp.puschmann@...ix.com>
CC:     Aymen Sghaier <aymen.sghaier@....com>,
        "herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "o.rempel@...gutronix.de" <o.rempel@...gutronix.de>
Subject: Re: [PATCH] crypto: caam: set hwrng quality level

On 2/13/2019 4:49 PM, Philipp Puschmann wrote:
> When quality is set to 0 this driver is not used as randomness source by
> HWRNG framework at all. So set the quality and finally make this driver
> work. The value of the quality was discussed before
> ( see see https://patchwork.kernel.org/patch/9850669/ ) and it is still a rough
> value.
> 
In the same thread you mention, the conclusion is that caamrng should be
properly configured (TRNG instead of DRBG) before claiming to be a reliable
hwrng entropy source.

Horia

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ