From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Tadeusz Struk <tadeusz.struk@intel.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 13:25:57 -0500 [thread overview]
Message-ID: <1449771957.2694.2.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151209235226.11783.57073.stgit@tstruk-mobl1>
On Wed, 2015-12-09 at 15:52 -0800, Tadeusz Struk 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...
Mimi
> Patches generated against cryptodev-2.6
> ---
>
> Tadeusz Struk (2):
> crypto: KEYS: convert public key to the akcipher api
> integrity: convert digsig to akcipher api
>
>
> crypto/asymmetric_keys/Kconfig | 2
> crypto/asymmetric_keys/Makefile | 7 -
> crypto/asymmetric_keys/pkcs7_parser.c | 12 +-
> crypto/asymmetric_keys/pkcs7_trust.c | 2
> crypto/asymmetric_keys/pkcs7_verify.c | 2
> crypto/asymmetric_keys/public_key.c | 64 +++------
> crypto/asymmetric_keys/public_key.h | 36 -----
> crypto/asymmetric_keys/rsa.c | 211 +++++++++++------------------
> crypto/asymmetric_keys/x509_cert_parser.c | 37 +----
> crypto/asymmetric_keys/x509_public_key.c | 17 +-
> crypto/asymmetric_keys/x509_rsakey.asn1 | 4 -
> include/crypto/public_key.h | 49 ++-----
> security/integrity/digsig_asymmetric.c | 10 -
> 13 files changed, 138 insertions(+), 315 deletions(-)
> delete mode 100644 crypto/asymmetric_keys/public_key.h
> delete mode 100644 crypto/asymmetric_keys/x509_rsakey.asn1
>
> --
> TS
> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-12-10 18:25 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 ` Mimi Zohar [this message]
2015-12-10 18:39 ` [PATCH 0/2] crypto: KEYS: convert public key " Tadeusz Struk
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=1449771957.2694.2.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.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=tadeusz.struk@intel.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).