From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <herbert@gondor.apana.org.au>, <davem@davemloft.net>
Cc: <linux-crypto@vger.kernel.org>, <smueller@chronox.de>,
<marcel@holtmann.org>, <Nicolas.Ferre@microchip.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [RFC PATCH v2 0/4] crypto: (ec)dh - add privkey generation support
Date: Wed, 17 May 2017 18:26:49 +0300 [thread overview]
Message-ID: <1495034813-27143-1-git-send-email-tudor.ambarus@microchip.com> (raw)
Hi,
This is an RFC to discuss how to support private key generation for dh and ecdh.
This is helpful in a user-space to kernel (ec)dh offload because the keys are
generated in kernel and never revealed to user-space.
Private key generation is also helpful to implement forward secrecy.
A public/private key system demonstrates the property of forward secrecy if it
creates new key pairs for each communication session. These key pairs are
generated on an as-needed basis and are destroyed after the session is over.
If an attacker were to record previous encrypted session data, they wouldn't be
able to decrypt it with possession of a long-term key.
There are crypto accelerators that are capable of generating and retaining
private keys without revealing them to software. This patch set is a
prerequisite for hardware private key generation support.
Changes in v2:
- free dh params in case of error
- code defensively in testmgr: use sizeof(*ptr) while in memcpy
v1 can be found at:
http://www.mail-archive.com/linux-crypto@vger.kernel.org/msg25176.html
Tudor Ambarus (4):
crypto: ecc - add privkey generation support
crypto: ecdh - allow user to provide NULL privkey
crypto: dh - allow user to provide NULL privkey
crypto: testmgr - add genkey kpp test
crypto/dh.c | 21 ++++++++
crypto/ecc.c | 20 +++++++
crypto/ecc.h | 14 +++++
crypto/ecdh.c | 4 ++
crypto/testmgr.c | 76 +++++++++++++++++++++++----
crypto/testmgr.h | 155 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
6 files changed, 279 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2017-05-17 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 15:26 Tudor Ambarus [this message]
2017-05-17 15:26 ` [RFC PATCH v2 1/4] crypto: ecc - add privkey generation support Tudor Ambarus
2017-05-28 18:44 ` Stephan Müller
2017-05-29 9:08 ` Tudor Ambarus
2017-05-29 9:23 ` Stephan Müller
2017-05-29 9:47 ` Tudor Ambarus
2017-05-29 9:56 ` Stephan Müller
2017-05-29 13:27 ` Tudor Ambarus
2017-05-17 15:26 ` [RFC PATCH v2 2/4] crypto: ecdh - allow user to provide NULL privkey Tudor Ambarus
2017-05-17 15:26 ` [RFC PATCH v2 3/4] crypto: dh " Tudor Ambarus
2017-05-28 18:50 ` Stephan Müller
2017-05-17 15:26 ` [RFC PATCH v2 4/4] crypto: testmgr - add genkey kpp test Tudor Ambarus
2017-05-26 13:44 ` Tudor Ambarus
2017-05-28 18:57 ` Stephan Müller
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=1495034813-27143-1-git-send-email-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=smueller@chronox.de \
/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).