From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: herbert@gondor.apana.org.au, dhowells@redhat.com,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/2] crypto: KEYS: convert public key to akcipher api
Date: Thu, 10 Dec 2015 10:39:32 -0800 [thread overview]
Message-ID: <5669C6E4.8030002@intel.com> (raw)
In-Reply-To: <1449771957.2694.2.camel@linux.vnet.ibm.com>
Hi Mimi,
On 12/10/2015 10:25 AM, Mimi Zohar wrote:
>> This patch set converts the module verification and digital signature
>> > code to the new akcipher API.
>> > RSA implementation has been removed from crypto/asymmetric_keys and the
>> > new API is used for cryptographic primitives.
>> > There is no need for MPI above the akcipher API anymore.
>> > Modules can be verified with software as well as HW RSA implementations.
> With these two patches my system doesn't even boot. Digging deeper...
>
It needs RSA implementation built-in.
Could you check if you have CONFIG_CRYPTO_RSA=y
Thanks
--
TS
next prev parent reply other threads:[~2015-12-10 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 23:52 [PATCH 0/2] crypto: KEYS: convert public key to akcipher api Tadeusz Struk
2015-12-09 23:52 ` [PATCH 1/2] crypto: KEYS: convert public key to the " Tadeusz Struk
2015-12-09 23:52 ` [PATCH 2/2] integrity: convert digsig to " Tadeusz Struk
2015-12-10 18:25 ` [PATCH 0/2] crypto: KEYS: convert public key " Mimi Zohar
2015-12-10 18:39 ` Tadeusz Struk [this message]
2015-12-10 19:37 ` Mimi Zohar
2015-12-10 21:56 ` Mimi Zohar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5669C6E4.8030002@intel.com \
--to=tadeusz.struk@intel.com \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=zohar@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).