On (06/10/15 17:09), Stephan Mueller wrote: > Hi Sergey, > > >Be more verbose and also report ->backend_cra_name when > >crypto_alloc_shash() or crypto_alloc_cipher() fail in > >drbg_init_hash_kernel() or drbg_init_sym_kernel() > >correspondingly. > > > >Example > > DRBG: could not allocate digest TFM handle: hmac(sha256) > > > >Signed-off-by: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx> > > Headscratch -- the Kconfig should have HMAC selected for compilation. When > HMAC is available (regardless whether it is a module or not), it is pulled in > by the kernel crypto API. Thus, there should not have been the error that HMAC > is missing. > > Can you send your .config file, please? > Hi Stephan, sure, will post it later (as soon as I get back to my laptop). -ss -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
