From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Keith Busch <keith.busch@wdc.com>, Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv5 nvme-cli 0/3] nvme-cli authentication support
Date: Fri, 12 Nov 2021 14:11:08 +0100 [thread overview]
Message-ID: <20211112131111.97599-1-hare@suse.de> (raw)
Hi all,
this patchset implements support for nvme in-band authentication.
It is cut against the current nvme-cli master branch, and requires a
libnvme patch 'Implement dhchap_key host and controller attributes'.
The implementation corresponds to the v5 version of the kernel patches
for implementing nvme in-band authentication.
As usual, comments and reviews are welcome.
Hannes Reinecke (3):
Add 'gen-dhchap-key' command
Add 'check-dhchap-key' function
nvme-connect: Add 'dhchap-secret' and 'dhchap-ctrl-secret' arguments
Documentation/nvme-check-dhchap-key.txt | 31 +++
Documentation/nvme-connect.txt | 17 ++
Documentation/nvme-gen-dhchap-key.txt | 52 +++++
Makefile | 17 +-
fabrics.c | 17 +-
nvme-builtin.h | 2 +
nvme.c | 276 ++++++++++++++++++++++++
util/argconfig.h | 1 +
util/base64.c | 105 +++++++++
util/base64.h | 7 +
10 files changed, 521 insertions(+), 4 deletions(-)
create mode 100644 Documentation/nvme-check-dhchap-key.txt
create mode 100644 Documentation/nvme-gen-dhchap-key.txt
create mode 100644 util/base64.c
create mode 100644 util/base64.h
--
2.31.1
next reply other threads:[~2021-11-12 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 13:11 Hannes Reinecke [this message]
2021-11-12 13:11 ` [PATCH nvme-cli 1/3] Add 'gen-dhchap-key' command Hannes Reinecke
2021-11-12 13:11 ` [PATCH nvme-cli 2/3] Add 'check-dhchap-key' function Hannes Reinecke
2021-11-12 13:11 ` [PATCH nvme-cli 3/3] nvme-connect: Add 'dhchap-secret' and 'dhchap-ctrl-secret' arguments Hannes Reinecke
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=20211112131111.97599-1-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.