From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: kernel failure while loading X.509 certificate Date: Wed, 17 Jan 2018 11:08:53 +0000 Message-ID: <11931.1516187333@warthog.procyon.org.uk> References: <88A6FE91-795D-4F17-BF8C-E597239A2C46@linaro.org> <48DEA233-E708-4661-B5F0-15CEC60877E4@linaro.org> <20180117051627.GA15527@zzz.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: dhowells@redhat.com, Eric Biggers , Arnd Bergmann , Ulf Hansson , Linus Walleij , Daniel Lezcano , Mark Brown , Vincent Guittot , John Stultz , Eric Biggers , crypto , Thorsten Leemhuis To: Paolo Valente Return-path: Received: from mx1.redhat.com ([209.132.183.28]:55609 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752276AbeAQLJC (ORCPT ); Wed, 17 Jan 2018 06:09:02 -0500 In-Reply-To: <88A6FE91-795D-4F17-BF8C-E597239A2C46@linaro.org> Content-ID: <11930.1516187333.1@warthog.procyon.org.uk> Sender: linux-crypto-owner@vger.kernel.org List-ID: If this happened during boot, it could be that you have an X.509 cert for which the digest algorithm isn't built into the kernel. David