From: Ignat Korchagin <ignat@cloudflare.com>
To: David Howells <dhowells@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kernel-team@cloudflare.com, lei he <helei.sig11@bytedance.com>,
Ignat Korchagin <ignat@cloudflare.com>
Subject: [PATCH v2 0/4] crypto, keys: add ECDSA signature support to key retention service
Date: Fri, 14 Oct 2022 11:07:33 +0100 [thread overview]
Message-ID: <20221014100737.94742-1-ignat@cloudflare.com> (raw)
Changes from v1:
* fixed code format
Kernel Key Retention Service[1] is a useful building block to build secure
production key management systems. One of its interesting features is
support for asymmetric keys: we can allow a process to use a certain key
(decrypt or sign data) without actually allowing the process to read the
cryptographic key material. By doing so we protect our code from certain
type of attacks, where a process memory memory leak actually leaks a
potentially highly sensitive cryptographic material.
But unfortunately only RSA algorithm was supported until now, because
in-kernel ECDSA implementation supported signature verifications only.
This patchset implements in-kernel ECDSA signature generation and adds
support for ECDSA signing in the key retention service. The key retention
service support was taken out of a previous unmerged patchset from Lei He[2]
[1]: https://www.kernel.org/doc/html/latest/security/keys/core.html
[2]: https://patchwork.kernel.org/project/linux-crypto/list/?series=653034&state=*
Ignat Korchagin (2):
crypto: add ECDSA signature generation support
crypto: add ECDSA test vectors from RFC 6979
lei he (2):
crypto: pkcs8 parser support ECDSA private keys
crypto: remove unused field in pkcs8_parse_context
crypto/Kconfig | 3 +-
crypto/Makefile | 4 +-
crypto/asymmetric_keys/pkcs8.asn1 | 2 +-
crypto/asymmetric_keys/pkcs8_parser.c | 46 +++-
crypto/ecc.c | 9 +-
crypto/ecdsa.c | 373 +++++++++++++++++++++++++-
crypto/ecprivkey.asn1 | 6 +
crypto/testmgr.c | 18 ++
crypto/testmgr.h | 333 +++++++++++++++++++++++
include/crypto/internal/ecc.h | 10 +
10 files changed, 787 insertions(+), 17 deletions(-)
create mode 100644 crypto/ecprivkey.asn1
--
2.30.2
next reply other threads:[~2022-10-14 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 10:07 Ignat Korchagin [this message]
2022-10-14 10:07 ` [PATCH v2 1/4] crypto: add ECDSA signature generation support Ignat Korchagin
2022-10-14 10:07 ` [PATCH v2 2/4] crypto: add ECDSA test vectors from RFC 6979 Ignat Korchagin
2022-10-14 10:07 ` [PATCH v2 3/4] crypto: pkcs8 parser support ECDSA private keys Ignat Korchagin
2022-10-14 10:07 ` [PATCH v2 4/4] crypto: remove unused field in pkcs8_parse_context Ignat Korchagin
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=20221014100737.94742-1-ignat@cloudflare.com \
--to=ignat@cloudflare.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=helei.sig11@bytedance.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-team@cloudflare.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).