On Tue, Nov 12, 2019 at 07:13:02AM -0800, Andrey Smirnov wrote: > > If I am reading the datasheet right reseeding should be done every > time CAAM is asked to generated random data. If you can guarantee that everytime the driver reads n bytes from the hardware, that the hardware is then reseeded with nbytes prior to that read, then it should be good enough. If the hardware only reseeds afterwards or reseeds with less than n bytes then it is not sufficient. > Even if prediction resistance is an acceptable approach, would it be > better to expose underlying TRNG and downgrade current CAAM hwrng code > to crypto rng API? If that's the best path forward, I am more than > happy to go that way in v2. If it offers true prediction resistance it should be good enough to use the drivers/char/hw_random interface. Otherwise please switch to the Crypto API RNG interface. Thanks, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
