Hi, Stephan,
On 29.05.2017 12:23, Stephan Müller wrote:
Am Montag, 29. Mai 2017, 11:08:38 CEST schrieb Tudor Ambarus:
Hi Tudor,
+ unsigned int nbytes = ndigits << ECC_DIGITS_TO_BYTES_SHIFT;
+
+ get_random_bytes(priv, nbytes);
Can you please use crypto_get_default_rng / crypto_rng_get_bytes /
crypto_put_default_rng?
Actually I tried this and I encountered some problems, I'm currently
debugging it.
When using the default rng and the run-time self tests are enabled,
the kernel is in a blocking state. What's worse is that the kernel
blocks before the console has the chance to be enabled and I can't see
anything :).
I suspect that the kernel blocks because the rng does not have enough
entropy. Could you please give me some hints?
Hm, there should be no blocking for the DRBG to initialize.
What happens if you compile that as a module and insmod it at runtime?
We will have a nop:
#ifdef CONFIG_CRYPTO_MANAGER_DISABLE_TESTS
/* a perfect nop */
int alg_test(const char *driver, const char *alg, u32 type, u32 mask)
{
printk(KERN_ERR "no op in alg_test");
return 0;
}
#else
...
#endif
If I further mangle it and change #ifdef with #ifndef then the tests are
passing.
Thanks,
ta
