linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: herbert@gondor.apana.org.au
Cc: keescook@chromium.org, jwboyer@redhat.com, smueller@chronox.de,
	richard@nod.at, tadeusz.struk@intel.com, steved@redhat.com,
	linux-kernel@vger.kernel.org, dhowells@redhat.com,
	linux-crypto@vger.kernel.org, james.l.morris@oracle.com,
	jkosina@suse.cz, zohar@linux.vnet.ibm.com, davem@davemloft.net,
	vgoyal@redhat.com
Subject: [PATCH 0/2] crypto: KEYS: convert public key to the akcipher API
Date: Wed, 12 Aug 2015 20:54:33 -0700	[thread overview]
Message-ID: <20150813035433.25108.3065.stgit@tstruk-mobl1> (raw)

This patch converts the module verification code to the new akcipher API.
RSA implementation from crypto/asymmetric_keys has been removed and the
new API is used for cryptographic primitives. The signature verification
has been moved into a new crypto/asymmetric_keys/rsa_pkcs1_v1_5.c file.
There is no need for MPI above the API anymore.
Modules can be verified with software as well as HW rsa implementations.

Also changed qat rsa implementation not to move data inside
the output buff similarly to SW.

---

Tadeusz Struk (2):
      crypto: KEYS: convert public key to the akcipher API
      crypto: qat - Don't move data inside output buffer


 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           |   59 +----
 crypto/asymmetric_keys/public_key.h           |   36 ---
 crypto/asymmetric_keys/rsa.c                  |  278 -------------------------
 crypto/asymmetric_keys/rsa_pkcs1_v1_5.c       |  232 +++++++++++++++++++++
 crypto/asymmetric_keys/x509_cert_parser.c     |   37 +--
 crypto/asymmetric_keys/x509_public_key.c      |   17 +-
 crypto/asymmetric_keys/x509_rsakey.asn1       |    4 
 drivers/crypto/qat/qat_common/qat_asym_algs.c |    3 
 include/crypto/public_key.h                   |   48 +---
 kernel/module_signing.c                       |   56 ++---
 security/integrity/digsig_asymmetric.c        |   11 -
 16 files changed, 304 insertions(+), 502 deletions(-)
 delete mode 100644 crypto/asymmetric_keys/public_key.h
 delete mode 100644 crypto/asymmetric_keys/rsa.c
 create mode 100644 crypto/asymmetric_keys/rsa_pkcs1_v1_5.c
 delete mode 100644 crypto/asymmetric_keys/x509_rsakey.asn1

--

             reply	other threads:[~2015-08-13  3:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-13  3:54 Tadeusz Struk [this message]
2015-08-13  3:54 ` [PATCH 1/2] crypto: KEYS: convert public key to the akcipher API Tadeusz Struk
2015-08-15 18:08   ` Stephan Mueller
2015-08-24 17:45     ` Tadeusz Struk
2015-08-13  3:54 ` [PATCH 2/2] crypto: qat - Don't move data inside output buffer Tadeusz Struk
2015-08-13 16:40   ` Tadeusz Struk
2015-08-14  5:14   ` Herbert Xu
2015-08-14  6:14     ` Tadeusz Struk
2015-08-14  6:26       ` Herbert Xu
2015-08-14 14:21         ` Tadeusz Struk
2015-08-17  8:48           ` Herbert Xu
2015-08-14 14:24         ` Tadeusz Struk
2015-08-17  8:50           ` Herbert Xu
2015-08-18  1:05             ` Tadeusz Struk
2015-08-18  2:39               ` Herbert Xu
2015-08-13 13:56 ` [PATCH 0/2] crypto: KEYS: convert public key to the akcipher API David Howells
2015-08-13 16:44   ` Tadeusz Struk
2015-08-13 14:23 ` [PATCH 1/2] " David Howells
2015-08-13 16:47   ` Tadeusz Struk
2015-08-14  1:09   ` Herbert Xu

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=20150813035433.25108.3065.stgit@tstruk-mobl1 \
    --to=tadeusz.struk@intel.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.l.morris@oracle.com \
    --cc=jkosina@suse.cz \
    --cc=jwboyer@redhat.com \
    --cc=keescook@chromium.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    --cc=smueller@chronox.de \
    --cc=steved@redhat.com \
    --cc=vgoyal@redhat.com \
    --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).