From: Raja Zidane <rzidane@nvidia.com>
To: <dev@dpdk.org>
Cc: <matan@nvidia.com>
Subject: [PATCH 0/2] crypto/mlx5: add support for plaintext import method
Date: Mon, 18 Apr 2022 14:10:03 +0300 [thread overview]
Message-ID: <20220418111005.2291-1-rzidane@nvidia.com> (raw)
Using crypto devs requires the user to log in and the supplied DEK to be
encrypted with a KEK (keys encryption key).
KEK is burned once on the nic, along with credentials for users,
and for a user to log in, he is needed to supply his creds wrapped with
the KEK.
A device comes out of the Mellanox factory with a pre-defined import
method for each algorithm. The defined method could be wrapped
mode, so the device can be used as described above, or
plaintext mode, without the need to log in and wrap supplied DEKs.
Raja Zidane (2):
common/mlx5: extend crypto capabilities
crypto/mlx5: support plaintext keys
doc/guides/cryptodevs/mlx5.rst | 17 ++++++++--
drivers/common/mlx5/mlx5_devx_cmds.c | 13 ++++++--
drivers/common/mlx5/mlx5_devx_cmds.h | 1 +
drivers/common/mlx5/mlx5_prm.h | 29 +++++++++++++++++
drivers/crypto/mlx5/mlx5_crypto.c | 43 +++++++++++++++---------
drivers/crypto/mlx5/mlx5_crypto.h | 3 +-
drivers/crypto/mlx5/mlx5_crypto_dek.c | 47 +++++++++++++++++++--------
7 files changed, 117 insertions(+), 36 deletions(-)
--
dependant on https://patchwork.dpdk.org/project/dpdk/patch/20220418110516.2105-1-rzidane@nvidia.com/
2.21.0
next reply other threads:[~2022-04-18 11:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 11:10 Raja Zidane [this message]
2022-04-18 11:10 ` [PATCH 1/2] common/mlx5: extend crypto capabilities Raja Zidane
2022-04-25 5:27 ` [EXT] " Akhil Goyal
2022-04-18 11:10 ` [PATCH 2/2] crypto/mlx5: support plaintext keys Raja Zidane
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=20220418111005.2291-1-rzidane@nvidia.com \
--to=rzidane@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.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).