From: hch@infradead.org (Christoph Hellwig)
Subject: NVMeoF Authentication
Date: Wed, 25 Apr 2018 22:33:10 -0700 [thread overview]
Message-ID: <20180426053310.GA10842@infradead.org> (raw)
In-Reply-To: <DE927C68B458BE418D582EC97927A9287FEC86DA@ORSMSX113.amr.corp.intel.com>
On Wed, Apr 25, 2018@07:43:05PM +0000, Gruher, Joseph R wrote:
> Hi folks-
>
> Does the Linux kernel NVMeoF initiator and target implementation support the Authentication Send and Authentication Receive commands from the NVMeoF spec for NVMe in-band authentication?? If not, is there any plan to implement?? Or is some other authentication method (beyond access control list) available?
Just the hostnqn lists. There currently isn't even any authentification
mechanism specified in NVMe, but a TP to propose one is going to be
posted to the technical working group soon.
prev parent reply other threads:[~2018-04-26 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 19:43 NVMeoF Authentication Gruher, Joseph R
2018-04-26 5:33 ` Christoph Hellwig [this message]
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=20180426053310.GA10842@infradead.org \
--to=hch@infradead.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